A2AMCP.dev / Migration
Exposing MCP Tool Servers as A2A v1.0.1 Agents
Bridge tool-level MCP backends into peer-to-peer A2A orchestration without duplicating business logic or weakening authorization.
Adapter Pattern (Zero Handler Rewrite)
- Keep MCP as the typed tool bus: keep your existing MCP handlers behind private mesh/VPC boundaries.
- Compile the public skill surface: export only approved read-only or policy-gated tools through a2amcp.dev — omit internal admin/debug tools from the A2A Card.
- Publish
/.well-known/agent-card.json: pin the RFC 8785 JCS digest from mcpa2a.dev in your release CI so peers detect unapproved skill drift. - Enforce bounded execution: map each incoming A2A task to a single allowlisted MCP tool call with strict timeout and schema validation.
Interoperability Cluster
Validate & JCS-hash your compiled Agent Card on mcpa2a.dev →