Zero Custom Code, Full GitHub Access: Wiring MCP Tools into Google ADK

Pranav Dhopey

5 min read

·

Jul 19, 2026

--

Listen

Share

Press enter or click to view image in full size

All Code Examples:: GitHub Repository

Enjoy free access via this friend link — no membership required.

TL;DR: Every tool you’ve given your ADK agents so far has meant writing Python — either a FunctionTool wrapper or a built-in like google_search. This part skips that entirely. Using McpToolset and StreamableHTTPConnectionParams, we point an agent straight at the remote GitHub MCP server and get repository, issue, and pull-request tools for free — zero wrapper functions written.

The Problem With “One Tool, One Function”

Here’s a scenario that comes up constantly in client engagements: someone wants an agent that can triage GitHub issues, summarize open PRs, and pull recent commits for a release note. The instinct is to start writing FunctionTools — list_issues(), get_pull_request(), list_commits() — and pretty soon you're maintaining a small SDK just to keep the agent's tool list in sync with the GitHub API surface.

That’s the pattern we’ve used through Part 1 (Basics) and Part 5 (AgentTool) of this series, and it works fine for two or three actions. It stops working the moment “GitHub” becomes “GitHub, Jira, and Slack” — you end up hand-rolling wrapper functions for services that already expose a…