OpenAgent Interoperability

OpenAgent Interoperability is a standards profile and conformance toolkit for agents that need to discover one another, exchange durable work, and use tools across runtime boundaries.

It does not define a new wire protocol:

• A2A v1 carries agent discovery, messages, durable tasks, status, artifacts, and cancellation.
• MCP carries tool, data, and device capabilities over remote Streamable HTTP.

The boundary is intentional: agents exchange work through A2A and access capabilities through MCP.

Runtime compatibility

Any runtime that can connect to a remote MCP server can use OpenAgent capabilities. This includes Codex-, Gemini-, and Claude-style agent hosts when their product or adapter supports remote MCP.

That does not mean those runtimes natively speak A2A. A runtime participates in A2A through its own A2A client/server support or a standards-preserving adapter. The adapter maps A2A tasks to the runtime without changing the public A2A contract.

What is included

• A concise interoperability profile for A2A v1 and MCP 2026-07-28
• Guidance for dual-era MCP deployments that also serve 2025-11-25 clients
• JSON fixtures and profile schemas
• A provider-neutral TypeScript validator and read-only endpoint probe
• Security and contribution guidance suitable for a public project

The profile is deliberately narrow. It tests a dependable common baseline and does not imply support for streaming, push notifications, files, or extensions unless an Agent Card advertises them.

Quick start

Requires Node.js 20 or newer.

npm ci
npm run check

Validate local fixtures:

npm run conformance -- fixtures

Probe a public A2A Agent Card and a remote MCP discovery endpoint:

npm run conformance -- probe \
  --a2a https://agents.openagent.md \
  --mcp https://api.openagent.md/mcp

If either endpoint requires a bearer token, set OPENAGENT_TOKEN in the environment. The probe only performs A2A discovery and MCP server/discover; it never submits work or calls a tool.

Status

This repository is an initial public interoperability profile. Protocol specifications remain authoritative. Profile requirements may tighten before a 1.0.0 release, but they will not replace or fork A2A or MCP.

See the interoperability profile, runtime integration, and conformance guide.

License

Apache License 2.0. See LICENSE.