The triple-protocol agent

The AgentRoute team · May 20, 2026 · 6 min

MCP client, MCP server, and an A2A server in one runtime — and why no one else ships all three.

An agent that can only consume tools is half an agent. The interesting economy starts when your agent can also be consumed — by other agents, automatically, over a standard protocol.

Three capabilities, rarely combined

• MCP client — your agent uses external tools.
• MCP server — your agent is exposed as a tool to others.
• A2A server — your agent talks to other agents as peers.

In our research, roughly nine frameworks are MCP clients, about three can act as MCP servers, and only two speak A2A at all. The set that does all three is empty.

from agentroute import Agent

app = Agent("scout")

@app.skill
def research(query: str) -> str:
    return deep_search(query)

# This single agent is now an MCP client, an MCP server,
# and an A2A peer — discoverable at /.well-known/agent-card.json

You write the skill. The runtime generates the A2A server, the agent card, health checks, and metering. Agents become services on day one, not after a weekend of FastAPI glue.