a2a-mcp-bridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BRIDGE_STATE_KEY | Yes | A base64url-encoded 32-byte AES-256 key used to seal and unseal task handles. Must be identical across every bridge instance serving the same clients. | |
| BRIDGE_INSTANCE_ID | No | A short identifier for this process, surfaced on every HTTP response as the Bridge-Instance-Id header and included in structured log lines. Falls back to a random id if unset. | |
| BRIDGE_AGENTS_CONFIG | Yes | A JSON array of agent entries: {"agent_id": "...", "base_url": "...", "headers": {...}}. Required. | |
| BRIDGE_STATE_KEY_PREVIOUS | No | A second key of the same shape, consulted only when unsealing (never when sealing new handles). Set this alongside a new BRIDGE_STATE_KEY while rotating keys. |
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
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/aarushitandon0/a2a-mcp-bridge'
If you have feedback or need assistance with the MCP directory API, please join our Discord server