A2A MCP
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@A2A MCPask my A2A agent to list my unread emails"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
A2A MCP
@cognicellai/a2a-mcp is an MCP server that bridges local MCP hosts to A2A v1-compatible agents.
It exposes the A2A v1 client operation surface through MCP tools and routes A2A calls through the official @a2a-js/sdk client.
Install From npm
Install it from the official npm registry:
npm install -g @cognicellai/a2a-mcpOr run it directly with npx:
A2A_MCP_CONFIG=/absolute/path/to/a2a-mcp.config.yaml npx -y @cognicellai/a2a-mcpFor MCP host setup, see docs/host-setup.md. For end-to-end usage examples covering no-auth, API-key, and machine-to-machine OAuth A2A agents, see docs/user-guide.md.
The installed CLI command is a2a-mcp.
For maintainers preparing a release, see docs/release.md.
Related MCP server: Agent Aggregator
Development From Source
npm install
npm run build
npm test
npm run typecheck
npm run lint:docsStart the MCP server over stdio:
A2A_MCP_CONFIG=./a2a-mcp.config.example.yaml npm run devConfiguration
Agents are configured by alias. Credentials are referenced by profile and resolved from the local environment; token values are never accepted as MCP tool arguments.
See a2a-mcp.config.example.yaml.
Agent Card signature handling is fail-closed by default: unsigned cards are accepted with signaturePolicy: "ifPresent", but signed cards are rejected until trust-root-backed signature verification is implemented. Use signaturePolicy: "disabled" only for explicitly trusted local or development agents.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
Discover and call AI agents via MCP. Supports A2A agents and platform agents with async tasks.
Agent-native collaboration network: orchestrate a team of long-running agents from any MCP client.
Your org's AI agents, tasks, runs, search, and brain files as MCP tools and resources.
Remote MCP server to read and manage your Atako AI agents, messages, files, and integrations.
31
Related MCP Servers
- AlicenseBqualityFmaintenanceExposes OpenClaw tools (web search, page fetching, browser automation, PDF analysis, messaging, inter-agent communication, Canvas) as MCP tools for ACP agents.7-
- AlicenseAqualityDmaintenanceAggregates tools from multiple MCP servers, acting as a proxy to provide unified access to various AI agents and tools.10153MIT
- AlicenseAqualityCmaintenanceExposes A2A (Agent-to-Agent) protocol as MCP tools, enabling Goose to call remote A2A agents via External Subagent mechanism.6181MIT
- AlicenseNot gradedqualityAmaintenanceAn MCP bridge that exposes A2A agents as tools in VS Code agent chat, enabling natural language delegation to remote agents with multi-turn conversation and configurable authentication.121Apache 2.0