Expose A2A tools through MCP
Handler can expose A2A protocol operations through an MCP server so other tools can call the same card, message, task, session, and auth operations.Configure your agent harness
Most users do not starthandler mcp manually. Instead, add it to your agent’s
MCP server configuration so the agent harness launches Handler when it needs the
tools.
Amp or Pi example
Use the same command shape for Amp, Pi, or any MCP client that supports stdio servers:Run it manually for debugging
For local debugging, you can start the stdio server yourself:stdio, which is what most local MCP clients expect.
Available transports
Start the MCP server with the default stdio transport:stdio for local tool integrations and the HTTP-based transports when you
need a networked MCP endpoint.
What the MCP server exposes
The server provides tools across five areas:- card lookup and validation
- message sending
- task inspection, cancellation, and push config
- saved session inspection and cleanup
- credential storage and removal
Typical workflow
One common pattern is:- Configure one or more A2A servers in Handler.
- Add
handler mcpto your agent harness MCP config. - Connect your MCP client.
- Use MCP tools to inspect cards, send messages, and manage tasks against those agents.