Agent Wealth HubFree public resources
中文 EN العربية

Back to catalog / Agent interoperability

Expose an ADK agent as one MCP tool for other clients

Wrap an agent and its tools behind an MCP server so compatible clients can delegate through one bounded entry point.

Goal

Let non-ADK clients invoke the agent over MCP and receive only its final response.

Steps

  1. Choose an agent to expose and define input, output, data permissions, and request limits. [mcp]
  2. Call to_mcp_server(agent) to expose the whole agent as one MCP tool; clients do not see its internal tools. [mcp]
  3. Use a local Inspector or test client to verify the tool list and end-to-end response. [mcp]
  4. Protect transport and authentication in deployment and restrict clients and request rates. [mcp]

How to verify

Clients discover only the intended agent entry point, test requests return complete results, and unauthorized requests are rejected.

Troubleshooting

If internal tools appear, check that the MCP export registers the whole agent rather than individual tools; tighten server authorization and retest.

Permissions

Prerequisites

Permissions

Limitations

This procedure follows Google ADK at the pinned revision; other versions, models, or remote services may differ in APIs and event semantics. Recheck permissions, retention, and recovery before production.

Pinned upstream source

https://github.com/google/adk-python/blob/e9b74d36140f2594b24c481fb7a3825b2cb01e96/docs/guides/tools/mcp_tool/agent_to_mcp/index.md

Repository
google/adk-python
File path
docs/guides/tools/mcp_tool/agent_to_mcp/index.md
Pinned commit
e9b74d36140f2594b24c481fb7a3825b2cb01e96
Source checked
2026-10-14 · Reviewed against the pinned upstream source

Repository metrics

These values describe the upstream repository, not popularity or likes for an individual skill or playbook.

Stars
Not collected
Forks
Not collected
Observed at
Not collected

No metrics snapshot is available yet.

License: Apache-2.0

Main topic

When to use a Skill or MCP

Related resources