MCPA2A.dev / Migration
MIGRATION GUIDE · v0.x → A2A v1.0.1

Upgrading Pre-1.0 Agent Manifests to A2A v1.0.1

Resolve breaking field renames, discovery path changes, and unsigned card drift in minutes.

Breaking Changes: Draft v0.x → v1.0.1

AreaLegacy Draft (v0.2 / v0.3)A2A v1.0.1 Requirement
Well-Known Path/.well-known/agent.json/.well-known/agent-card.json (keep 301 redirect from legacy path)
Version FieldImplicit or omittedExplicit "protocolVersion": "1.0.1"
Skills SchemaLoose action stringsStructured skills[] with unique id, name, description, and tags
IntegrityRaw unsigned JSONRFC 8785 JCS canonicalization + SHA-256 digest pin

Recommended Pipeline

If your backend exposes MCP tools, do not hand-maintain two diverging manifests: lint your MCP server on modelcontextpro.dev, compile its A2A v1.0.1 card deterministically on a2amcp.dev, and verify the JCS digest on mcpa2a.dev in CI.

Interoperability Cluster

Validate upstream MCP 2026-07-28 tool manifests on modelcontextpro.dev →