a2a-mcp-bridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HOST | No | Host to bind the HTTP transport to. | 127.0.0.1 |
| MCP_PORT | No | Port to bind the HTTP transport to. | 3737 |
| A2A_BASE_URL | Yes | Base URL of the A2A host (e.g. https://your-a2a-host.example.com). Required, no default. | |
| A2A_AGENT_PATH | Yes | Path segment identifying the agent (e.g. /api-endpoint/your-agent). Required, no default. | |
| A2A_AGENT_LABEL | No | Optional label for the agent; becomes the tool title shown to the model. | |
| MCP_SESSION_TTL_MS | No | Idle session timeout for Streamable HTTP sessions in milliseconds (default 30 minutes). | 1800000 |
| MCP_ALLOWED_ORIGINS | No | Comma-separated list of allowed origins for HTTP transport, or `*` to disable origin checking. | |
| A2A_AGENT_DESCRIPTION | No | Optional description for the agent; becomes the tool description shown to the model. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ask_agentA | Send a message to the A2A agent 'the A2A agent' and get its reply. If the agent calls its own internal tools while answering, those calls are reported alongside the answer. Multi-turn context is preserved automatically across calls; set new_conversation=true to start over. Tool-using turns can take 15-60s. Also returns structured content: answer, tool_calls[{tool,text,parallel,at}], citations, followups, data, partial, context_id, turn, elapsed_ms. |
| get_last_traceA | Return the full detail of the most recent ask_agent turn: every internal tool call the agent made, its citations, structured data blocks, and — with raw=true — the untouched A2A response parts. Use this to see how the agent reached an answer. |
| get_agent_cardA | Fetch the A2A agent card for 'the A2A agent' — its name, version, capabilities, skills, supported input/output modes, and security schemes. |
| reset_conversationA | Clear the stored transcript so the next ask_agent call starts a brand-new conversation. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool serves a clearly distinct purpose: ask_agent for interaction, get_last_trace for inspecting the latest turn, get_agent_card for metadata, and reset_conversation for state management. There is no overlap between them.
All tool names follow the same verb_noun snake_case pattern (ask_agent, get_last_trace, get_agent_card, reset_conversation). The style is uniform and predictable.
Four tools is a well-scoped set for a single-agent bridge. Each tool covers an essential function without redundancy or bloat.
The tool surface covers the full lifecycle of interacting with the A2A agent: sending messages, inspecting agent capabilities, reviewing trace details, and resetting conversation state. No obvious dead ends or missing operations for this narrow domain.