Files
Wei Sun (Jack) fa5c546a55 fix(tools): Add proper cleanup for AgentTool to prevent MCP session errors
Merge https://github.com/google/adk-python/pull/3411

## Summary

Fixes AgentTool cleanup to prevent MCP session errors by calling `runner.close()` after sub-agent execution.

## Problem

When using AgentTool with MCP tools, the runner cleanup happened during garbage collection in a different async task context, causing:
```
RuntimeError: Attempted to exit cancel scope in a different task than it was entered in
```

## Solution

- Call `await runner.close()` immediately after sub-agent execution in AgentTool
- This ensures MCP sessions and other resources are cleaned up in the correct async task context
- Updated test mock to include the close() method

## Demo Agents

Added two comprehensive demo agents showing how to use AgentTool with MCP tools:

### mcp_in_agent_tool_remote (SSE mode)
- Uses HTTP/SSE connection to remote MCP server
- Zero-installation setup with `uvx`
- Demonstrates server-side MCP deployment pattern

### mcp_in_agent_tool_stdio (stdio mode)
- Uses subprocess connection with automatic server launch
- Fully automatic setup with `uvx` subdirectory syntax
- Demonstrates embedded MCP deployment pattern

Both demos:
- Use Gemini 2.5 Flash
- Include example prompts for JSON Schema exploration
- Have comprehensive READMEs with architecture diagrams
- Follow ADK agent structure conventions

## Testing

-  All existing unit tests pass
-  Manual testing with both SSE and stdio modes
-  Verified cleanup happens in correct async context
-  No more cancel scope errors with MCP tools

## Related

- Fixes #1112
- Related to #929

Co-authored-by: Wei Sun (Jack) <weisun@google.com>
COPYBARA_INTEGRATE_REVIEW=https://github.com/google/adk-python/pull/3411 from google:fix/agent-tool-mcp-cleanup 9ae753b5a4
PiperOrigin-RevId: 828651896
2025-11-05 15:23:39 -08:00

2.4 KiB

AgentTool with MCP Demo (Stdio Mode)

This demo shows how AgentTool works with MCP (Model Context Protocol) toolsets using stdio mode.

Stdio vs SSE Mode

This demo uses stdio mode where the MCP server runs as a subprocess:

  • Simpler setup - No need to start a separate server
  • Auto-launched - Server starts automatically when agent runs
  • Local process - Uses stdin/stdout for communication

For the SSE (remote server) version, see mcp_in_agent_tool_remote.

Setup

No installation required! The MCP server will be launched automatically using uvx when you run the agent.

The demo uses uvx to fetch and run the MCP simple-tool server directly from the GitHub repository's subdirectory:

uvx --from 'git+https://github.com/modelcontextprotocol/python-sdk.git#subdirectory=examples/servers/simple-tool' \
    mcp-simple-tool

This happens automatically via the stdio connection when the agent starts.

Running the Demo

adk web contributing/samples

Then select mcp_in_agent_tool_stdio from the list and interact with the agent.

Try These Prompts

This demo uses Gemini 2.5 Flash as the model. Try these prompts:

  1. Check available tools:

    What tools do you have access to?
    
  2. Fetch and summarize JSON Schema specification:

    Use the mcp_helper to fetch https://json-schema.org/specification and summarize the key features of JSON Schema
    

Architecture

main_agent (root_agent)
  │
  └── AgentTool wrapping:
        │
        └── mcp_helper (sub_agent)
              │
              └── McpToolset (stdio connection)
                    │
                    └── MCP Server (subprocess via uvx)
                          │
                          └── uvx --from git+...#subdirectory=... mcp-simple-tool
                                │
                                └── Website Fetcher Tool