a2a-mcp-bridge
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@a2a-mcp-bridgetell the home ops agent to run a system update"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
A2A Agent Bridge
Small A2A bridge experiments for OpenClaw/Home Ops agent-to-agent messaging.
This repository contains two pieces:
a2a-agent-bridge/: an HTTP A2A server exposing an Agent Card, JSON-RPC endpoint, and/healthz.a2a-mcp-bridge/: a stdio MCP server that lets MCP-capable agents call an A2A endpoint.
The A2A server is intentionally minimal and in-memory. It is useful as a real protocol target for the A2A Inspector and for wiring agent clients, but it is not yet a durable multi-agent queue.
A2A Server
Build locally:
docker build -t a2a-agent-bridge .Run locally:
docker run --rm -p 8080:8080 \
-e A2A_AGENT_NAME="Home Ops Agent Bridge" \
-e A2A_BASE_URL="http://localhost:8080" \
a2a-agent-bridgeEndpoints:
GET /healthzGET /.well-known/agent-card.jsonPOST /for A2A JSON-RPC
Related MCP server: A2A MCP Server
MCP Bridge
The MCP bridge lives in a2a-mcp-bridge/ and can be run with:
cd a2a-mcp-bridge
uv run a2a-mcp-bridgeSet A2A_AGENT_URL to point at the target A2A server.
Home Ops
Home Ops should consume this repository via the published GHCR image rather than storing the A2A server source in a ConfigMap.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
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/clawd-ops/a2a-agent-bridge'
If you have feedback or need assistance with the MCP directory API, please join our Discord server