Skip to content

Agent protocol support ​

This reference describes the protocol adapters in the repository, reviewed on 2026-11-16. An implemented adapter is source-level support, not a claim that a deployment has passed interoperability, load or production acceptance.

For the role of each protocol, see How agent protocols fit together.

Transport surfaces ​

ProtocolShared NATS adapterLocal surfaceRemote surface
A2Aa2a-nats client and servera2a-nats-stdioa2a-nats-http for local agents behind NATS; a2a-bridge for the separate HTTP cross-binding edge, requiring external TLS termination for HTTPS
ACPacp-nats and its bridge traitsacp-nats-stdioacp-nats-server, using the official SDK HTTP and WebSocket transport
MCPmcp-nats, implementing the official Rust SDK transport traits for both rolesmcp-nats-stdiomcp-nats-server, serving Streamable HTTP on /mcp

NATS subjects and bridge configuration are repository-specific bindings. Their existence does not mean upstream protocol clients connect directly to NATS.

A2A ​

Implemented surfaces ​

  • Message send and streaming, task get/list/cancel/resubscribe, push notification configuration and agent-card retrieval have typed method and subject mappings.
  • Task events use JetStream-backed paths. The client and server adapters carry the protocol between callers and agent implementations.
  • The HTTP adapter exposes JSON-RPC, streaming, REST routes and agent-card discovery at /.well-known/agent-card.json.
  • The gateway owns layered policy enforcement and audit on its ingress path. The separate a2a-bridge HTTP edge obtains caller-scoped NATS credentials through the auth callout. Its default enforce mode requires verified AAuth proof of possession; development-only shadow can admit a failed proof and off skips proof verification.

Boundaries ​

The local HTTP adapter, cross-binding edge and gateway are different components. Their security properties depend on the configured path, caller credentials and broker permissions. Do not infer authenticated public ingress from the presence of an HTTP listener alone.

The local HTTP adapter routes directly to agent subjects by default. Enable A2A_USE_GATEWAY to send its calls through gateway ingress.

The a2a-bridge binary binds a TCP listener and serves plain HTTP with axum::serve. An external reverse proxy or ingress must terminate TLS for public HTTPS. The repository provisions bridge NATS credentials and a replay bucket, but does not define a bridge deployment with a TLS-terminating component.

The adapters do not implement an agent's business behavior or the platform's definition/revision registry. Task transport is distinct from the proposed workflow execution model.

Source and decisions ​

ACP ​

Implemented surfaces ​

The bridge routes initialization and authentication, session creation/loading, prompts and cancellation, session management, provider operations and supported extensions. Client callbacks include file access, permission requests, session updates, terminal operations and session-scoped elicitation.

The remote listener uses the official SDK's HTTP and WebSocket transport, with compatibility layers for Origin enforcement, protocol-version validation and SSE buffering behavior.

The ACP conformance matrix is the authority for exact methods, payload variants, dependency pins and observable remote transport differences. Consult it when upgrading the SDK or comparing an upstream client with this bridge.

Known gaps ​

  • Request-scoped native MCP messages (mcp/message) are not routed. Preserving MCP capability payloads does not implement their lifecycle.
  • Connection-scoped auth/status_update push notifications and pre-session elicitation do not have a destination in the session-scoped client routing.
  • Proxy-chain initialization and successor handoff are not supported by this agent endpoint.
  • HTTP and WebSocket delivery do not establish full conformance with the evolving remote transport RFD. The matrix records the adopted SDK's behavior and remote transport differences.
  • Remote caller authentication and caller-bound subjects remain draft work under ADR#0087.

Source and operations ​

MCP ​

Implemented surfaces ​

  • The shared NATS adapter implements transport connections for MCP client and server roles using the official Rust SDK, rmcp.
  • The HTTP proxy forwards tools, resources, resource subscriptions, prompts, completions, discovery, supported task operations and custom requests. Server requests and notifications can travel back to the HTTP client.
  • MCP NATS bodies preserve canonical JSON-RPC messages. Selected MCP routing headers and request metadata survive the HTTP proxy; arbitrary HTTP headers and caller credentials are not forwarded as protocol metadata.
  • The stdio bridge and Streamable HTTP listener connect clients to a selected NATS-backed MCP server. The backend determines available capabilities.

Boundaries ​

mcp-nats is a protocol transport. It does not provide a managed tool registry, per-tool policy enforcement or third-party OAuth custody. Ordinary NATS subscriptions do not imply NATS micro discovery or queue-balanced service behavior.

The Streamable HTTP listener's allowed-host check is a DNS-rebinding defense, not caller authentication. Its configuration sets allowed hosts without setting allowed origins, so it does not enforce Origin validation. It uses a shared NATS connection with generated client peer IDs. The verified caller boundary remains proposed in ADR#0087.

The connector MCP authorization reference describes a separate outbound credential-custody contract. That design is not evidence that inbound MCP authorization or the managed connector service is deployed.

Source and decisions ​

Upstream protocols ​

Released under the Apache License 2.0.