Robert
09b588326c
agent-builder.build (and any long-running skill) takes minutes — LLM loop + sandbox tests + deploy + wait-for-live-card. A plain JSON POST to /mcp gets killed by ingress idle timeouts (~60s on traefik) and the gateway sees "fetch failed" while the upstream is still running. UpstreamAgent.callTool now negotiates ``Accept: text/event-stream`` on tools/call. We drain SSE frames, return the final tools/call result, and fall back to plain JSON if the upstream doesn't speak SSE (older a2a-pack). Elicit relaying isn't wired yet; for now any elicitation/create frame is ignored. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
a2amcp
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 login
npx -y a2amcp add <agent-name>
npx -y a2amcp doctor
Add it to your MCP client config:
{
"mcpServers": {
"a2a": {
"command": "npx",
"args": ["-y", "a2amcp"]
}
}
}
Restart the client after adding or removing agents.
Commands
a2amcp login # save control-plane credentials
a2amcp whoami # show current account
a2amcp agents # list agents visible to your account
a2amcp add <name> # expose one agent through this gateway
a2amcp list # list locally enabled agents
a2amcp remove <name> # stop exposing an agent
a2amcp doctor # probe enabled agents and count tools
a2amcp logout # clear local credentials
Running a2amcp with no command starts the MCP gateway over stdio.