No proper doucmentation for agent to mcp with release 2.5.0

[deepakbatham572]

Exposes an ADK agent as an MCP server, the MCP counterpart of to_a2a, so
MCP hosts such as Antigravity, Claude Code, and Codex can drive an ADK agent. The agent is registered as a single MCP tool backed by a Runner, with intermediate
events surfaced as MCP progress notifications. Ships @experimental behind
the existing mcp extra.

there is not such proper doucmentation to use this feature ..

[N-Garai]

Hi,can i work on this?

[Cnashn]

The to_mcp_server API is documented in the adk-python repo at docs/guides/tools/mcp_tool/agent_to_mcp/index.md, but the official docs site had no page for it, while the A2A counterpart to_a2a does. That gap is likely why it was hard to find.

I opened a docs-site PR to add an "Expose an ADK agent as an MCP server" quickstart under the MCP section: google/adk-docs#1981. It mirrors the A2A exposing quickstart and is grounded in the actual to_mcp_server signature. Happy to adjust based on maintainer feedback.

[surajksharma07]

@deepakbatham572 Thanks for flagging this — to_mcp_server does have a guide in the repo (docs/guides/tools/mcp_tool/agent_to_mcp/index.md), it just never made it onto the docs site the way to_a2a did.

@Cnashn already opened google/adk-docs#1981 to add that page, so this should be closed once that merges.

Separate nit while I was in there: the in-repo guide links to a mcp_serve_agent sample that doesn't actually exist yet — might be worth adding or fixing that link too!