A2A Mesh

Independent TypeScript runtime and toolkit for the Agent2Agent protocol.

Why A2A Mesh?

A2A Mesh combines runtime, client, registry, adapters, MCP bridge, transports, CLI diagnostics, schemas, and conformance output in one TypeScript workspace. It is designed for teams that need a fast local A2A loop and operational readiness checks.

Start here

1. Install the core package and CLI.
2. Follow the Quick Start for the shortest code path.
3. Run the 5-minute demo to validate an Agent Card and send a task.
4. Review the production checklist before a shared deployment.

What it includes

Surface	Use it for
Runtime and client	Agent Cards, JSON-RPC messages, tasks, artifacts, and task status transitions.
Registry	Discovery, health polling, exports, imports, and operator diagnostics.
CLI	Validate, discover, send, monitor, benchmark, conformance, scaffold, and release checks.
Adapters and bridge	Provider/framework adapters plus A2A-to-MCP request mapping.
Transports	HTTP/SSE baseline plus WebSocket and gRPC package surfaces.
Schemas and tests	JSON Schema artifacts, conformance reports, and smoke-testable examples.

Decision guide

• Use Official SDKs vs A2A Mesh to decide whether this toolkit belongs beside or instead of a first-party SDK in your project.
• Use Architecture when package boundaries or runtime responsibilities change.
• Use Security, Threat Model, and Production Checklist before production traffic.
• Use Release Process for package publishing and provenance guardrails.

Documentation map

• Install
• Quick Start
• 5-minute Demo
• Examples
• Architecture
• Compatibility
• Protocol Compatibility
• Security
• Threat Model
• Production Checklist
• Official SDKs vs A2A Mesh
• Release Process
• Packages