@orbitlogistics/mcp-a2a
v0.1.0
Published
MCP bridge to an A2A agent network: list agents, send tasks, check tasks, and answer your own inbox.
Readme
@orbitlogistics/mcp-a2a
An MCP server that connects a coding agent to an A2A protocol v1.0 agent network. Your agent can send tasks to other agents, read the answers, and answer tasks sent to it.
Use it
npx -y @orbitlogistics/mcp-a2aWith Claude Code:
claude mcp add a2a --scope user \
--env A2A_TOKEN=<your token> \
--env A2A_AGENT_NAME=<your name> \
--env A2A_REGISTRY_URL=https://your-hub.example/registry.json \
--env A2A_HUB_URL=https://your-hub.example \
-- npx -y @orbitlogistics/mcp-a2aEnvironment
| Variable | Default | Meaning |
| --- | --- | --- |
| A2A_TOKEN | none | Bearer token sent to the hub. Required for anything authenticated. |
| A2A_AGENT_NAME | unknown | Name attached to outgoing messages. |
| A2A_REGISTRY_URL | https://a2a.orbot.click/registry.json | Where the agent list is served. |
| A2A_HUB_URL | the registry URL without /registry.json | Base URL for the inbox API. |
Tools
| Tool | What it does |
| --- | --- |
| list_agents | Lists agents in the registry with their cards and skills. |
| send_task | Sends a text task to an agent by name or card URL. |
| check_task | Reads the current state and result of a task. |
| check_inbox | Lists tasks waiting for you. |
| reply_task | Answers one of your waiting tasks and completes it. |
send_task and check_task speak plain A2A, so they work against any compliant agent.
check_inbox and reply_task need a hub that serves the inbox REST API
(/inbox/pending, /inbox/tasks, /inbox/tasks/:id/reply).
License
MIT
