A2A MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| a2a_send_messageA | Send a message to an Agent-to-Agent (A2A) protocol compliant agent. This tool establishes communication with an A2A agent and sends a text message. The agent may respond immediately with a message or return a task object for asynchronous processing. Args:
Returns: JSON response containing either:
The response may include multiple parts (text, images, etc.) depending on the agent's capabilities. Examples:
Error Handling:
|
| a2a_get_taskA | Retrieve the status and details of an A2A task by its ID. This tool fetches information about a previously created task, including its current status, progress, and any generated artifacts. Args:
Returns: JSON response containing task information:
Examples:
Error Handling:
|
| a2a_cancel_taskA | Cancel a running A2A task. This tool requests cancellation of an active task. The agent will attempt to gracefully stop the task execution and update its status to "canceled". Args:
Returns: JSON response confirming the cancellation request:
Note: Cancellation may not be immediate. The task status should transition to "canceled" once the agent completes the cancellation process. Examples:
Error Handling:
|
| a2a_get_agent_cardA | Retrieve an agent's card containing metadata and capability information. This tool fetches the agent card which describes what the agent can do, its configuration, supported features, and other metadata. Args:
Returns: JSON response containing the agent card with:
Agent cards follow the A2A protocol specification and help clients understand how to interact with the agent. Examples:
Error Handling:
|
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/ericabouaf/a2a-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server