a2a-mcp-bridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| A2A_AGENT_URL | No | Default A2A agent endpoint (also overridable per tool call). | http://localhost:8001 |
| A2A_TIMEOUT_SECONDS | No | HTTP client timeout — raise this for slow/long-running agents. | 300 |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_agent_cardB | Fetch capabilities (name, description, skills) of an A2A agent. |
| send_a2a_messageA | Send a message to an A2A agent and return its final text response. The response ends with an Long-running agent pipelines are expected: progress notifications are emitted while the task runs, so tune A2A_TIMEOUT_SECONDS rather than treating a slow response as a hang. If the call does time out after the task started, the error names the task_id -- the task keeps running server-side and get_a2a_task can retrieve its result. |
| get_a2a_taskA | Fetch the current state and result of a previously started A2A task. Use this when send_a2a_message timed out or errored after the task had
already started: the task keeps running server-side, and this retrieves
its status and any output by the task_id from the error message or the
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/ytugarev/a2a-mcp-bridge'
If you have feedback or need assistance with the MCP directory API, please join our Discord server