Robert
f0f6fe9672
The @a2a scope on npm is owned by a different account, so PUT against the registry 404'd. Move to @a2amcp/mcp (scope we control) and bump the version so the publish workflow has a fresh tag to push. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@a2amcp/mcp
MCP gateway for a2acloud agents. It runs locally as a stdio MCP server and exposes deployed A2A agents as tools to Claude Code, Cursor, and other MCP clients.
Quickstart
npx -y @a2amcp/mcp login
npx -y @a2amcp/mcp add <agent-name>
npx -y @a2amcp/mcp doctor
Add it to your MCP client config:
{
"mcpServers": {
"a2a": {
"command": "npx",
"args": ["-y", "@a2amcp/mcp"]
}
}
}
Restart the client after adding or removing agents.
Commands
a2a-mcp login # save control-plane credentials
a2a-mcp whoami # show current account
a2a-mcp agents # list agents visible to your account
a2a-mcp add <name> # expose one agent through this gateway
a2a-mcp list # list locally enabled agents
a2a-mcp remove <name> # stop exposing an agent
a2a-mcp doctor # probe enabled agents and count tools
a2a-mcp logout # clear local credentials
Running a2a-mcp with no command starts the MCP gateway over stdio.