# How to integrate Google search console MCP with Google ADK

```json
{
  "title": "How to integrate Google search console MCP with Google ADK",
  "toolkit": "Google search console",
  "toolkit_slug": "google_search_console",
  "framework": "Google ADK",
  "framework_slug": "google-adk",
  "url": "https://composio.dev/toolkits/google_search_console/framework/google-adk",
  "markdown_url": "https://composio.dev/toolkits/google_search_console/framework/google-adk.md",
  "updated_at": "2026-05-12T10:13:44.771Z"
}
```

## Introduction

This guide walks you through connecting Google search console to Google ADK using the Composio tool router. By the end, you'll have a working Google search console agent that can fetch last week's top search queries, inspect indexing status for this url, list all sitemaps for your site through natural language commands.
This guide will help you understand how to give your Google ADK agent real control over a Google search console account through Composio's Google search console MCP server.
Before we dive in, let's take a quick look at the key ideas and tools involved.

## Also integrate Google search console with

- [ChatGPT](https://composio.dev/toolkits/google_search_console/framework/chatgpt)
- [OpenAI Agents SDK](https://composio.dev/toolkits/google_search_console/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/google_search_console/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/google_search_console/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/google_search_console/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/google_search_console/framework/codex)
- [Cursor](https://composio.dev/toolkits/google_search_console/framework/cursor)
- [VS Code](https://composio.dev/toolkits/google_search_console/framework/vscode)
- [OpenCode](https://composio.dev/toolkits/google_search_console/framework/opencode)
- [OpenClaw](https://composio.dev/toolkits/google_search_console/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/google_search_console/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/google_search_console/framework/cli)
- [LangChain](https://composio.dev/toolkits/google_search_console/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/google_search_console/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/google_search_console/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/google_search_console/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/google_search_console/framework/crew-ai)

## TL;DR

Here's what you'll learn:
- Get a Google search console account set up and connected to Composio
- Install the Google ADK and Composio packages
- Create a Composio Tool Router session for Google search console
- Build an agent that connects to Google search console through MCP
- Interact with Google search console using natural language

## What is Google ADK?

Google ADK (Agents Development Kit) is Google's framework for building AI agents powered by Gemini models. It provides tools for creating agents that can use external services through the Model Context Protocol.
Key features include:
- Gemini Integration: Native support for Google's Gemini models
- MCP Toolset: Built-in support for Model Context Protocol tools
- Streamable HTTP: Connect to external services through streamable HTTP
- CLI and Web UI: Run agents via command line or web interface

## What is the Google search console MCP server, and what's possible with it?

The Google search console MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Google Search Console account. It provides structured and secure access to your website’s search analytics and indexing data, so your agent can retrieve site lists, inspect URLs, manage sitemaps, and run detailed search performance queries on your behalf.
- Comprehensive site and sitemap management: Have your agent list all properties you own, fetch details about specific sitemaps, or submit new sitemaps for indexing to keep Google up to date.
- Automated URL inspection: Let your agent check the indexing status and uncover crawl or indexing issues for any URL in your properties, so you can spot and resolve problems quickly.
- Instant search analytics reporting: Ask your agent to pull granular performance metrics such as clicks, impressions, CTR, and average position for any site, page, or query segment.
- Bulk site and sitemap overview: Effortlessly retrieve a list of all sites and their associated sitemaps, making it easy to monitor your web presence at scale.
- Proactive index issue detection: Enable your agent to routinely review URLs and sitemaps for errors or warnings, helping you stay ahead of SEO issues without manual digging.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `GOOGLE_SEARCH_CONSOLE_ADD_SITE` | Add Site | Adds a site to the set of the user's sites in Google Search Console. This action registers a new property (site) in Google Search Console for the authenticated user. After adding the site, you will need to verify ownership through one of the available verification methods. The site URL must be properly formatted as either a URL-prefix property (with protocol) or a domain property (with sc-domain prefix). |
| `GOOGLE_SEARCH_CONSOLE_DELETE_SITE` | Delete Site | Removes a site from the user's Google Search Console sites. This action permanently removes a site property from the authenticated user's Search Console account. The site URL must be URL-encoded. Use this when you need to unregister a site from tracking in Search Console. |
| `GOOGLE_SEARCH_CONSOLE_GET_SITE` | Get Site | Retrieves information about a specific Search Console site. Use when you need to get site details including permission level for a specific property. |
| `GOOGLE_SEARCH_CONSOLE_GET_SITEMAP` | Get Sitemap | Retrieves sitemap metadata (submitted/indexed counts, errors, warnings, last-submission timestamps) for a specific sitemap in Search Console. Returns metadata only, not raw XML content. Note: numeric fields like `errors`, `warnings`, `submitted`, and `indexed` may be returned as strings; cast to int before comparisons. Values such as `contents.indexed` can lag several days after submission. |
| `GOOGLE_SEARCH_CONSOLE_INSPECT_URL` | Inspect URL | Inspects a URL for indexing issues and status in Google Search Console. Results may reflect cached data lagging real changes by several days. High-volume use can trigger 429 quota errors; limit to priority URLs. |
| `GOOGLE_SEARCH_CONSOLE_LIST_SITEMAPS` | List Sitemaps | Lists all sitemaps for a site in Google Search Console. Response fields `errors`, `warnings`, `contents.submitted`, and `contents.indexed` may be returned as strings; cast to integers before numeric operations. Evaluate these fields alongside `isPending` for sitemap health. |
| `GOOGLE_SEARCH_CONSOLE_LIST_SITES` | List Sites | Lists all verified sites (properties) owned by the authenticated user in Google Search Console. Response contains a siteEntry array — always iterate it, never assume a single object. Each entry includes permissionLevel, which varies per site; do not assume owner-level access for all returned properties. When calling downstream tools, use the site_url value exactly as returned, including protocol, subdomain, sc-domain: prefix, and trailing slash — any deviation causes empty results or permission errors. Empty siteEntry may indicate missing OAuth scopes or no verified properties. Newly added properties may not appear immediately due to propagation delay. |
| `GOOGLE_SEARCH_CONSOLE_SEARCH_ANALYTICS_QUERY` | Search Analytics Query | Queries Google Search Console for search analytics data including clicks, impressions, CTR, and position metrics. Only returns URLs with at least one impression; missing rows do not confirm non-indexing. Position is an impression-weighted average rank. |
| `GOOGLE_SEARCH_CONSOLE_SUBMIT_SITEMAP` | Submit Sitemap | Submits a sitemap to Google Search Console for indexing. This action registers or resubmits a sitemap for a verified property in Google Search Console. The sitemap file must be accessible at the specified URL and properly formatted as XML. Supported sitemap types include standard sitemaps, sitemap index files, RSS feeds, and Atom feeds. The authenticated user must have site owner or full user permissions for the property. After submission, Google will crawl and process the sitemap according to its standard indexing schedule. |

## Supported Triggers

None listed.

## Creating MCP Server - Stand-alone vs Composio SDK

The Google search console MCP server is an implementation of the Model Context Protocol that connects your AI agent to Google search console. It provides structured and secure access so your agent can perform Google search console operations on your behalf through a secure, permission-based interface.
With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster.

## Step-by-step Guide

### 1. Prerequisites

Before starting, make sure you have:
- A Google API key for Gemini models
- A Composio account and API key
- Python 3.9 or later installed
- Basic familiarity with Python

### 1. Getting API Keys for Google and Composio

Google API Key
- Go to [Google AI Studio](https://aistudio.google.com/app/apikey) and create an API key.
- Copy the key and keep it safe. You will put this in GOOGLE_API_KEY.
Composio API Key and User ID
- Log in to the [Composio dashboard](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs).
- Go to Settings → API Keys and copy your Composio API key. Use this for COMPOSIO_API_KEY.
- Decide on a stable user identifier to scope sessions, often your email or a user ID. Use this for COMPOSIO_USER_ID.

### 2. Install dependencies

Inside your virtual environment, install the required packages.
What's happening:
- google-adk is Google's Agents Development Kit
- composio connects your agent to Google search console via MCP
- python-dotenv loads environment variables
```bash
pip install google-adk composio python-dotenv
```

### 3. Set up ADK project

Set up a new Google ADK project.
What's happening:
- This creates an agent folder with a root agent file and .env file
```bash
adk create my_agent
```

### 4. Set environment variables

Save all your credentials in the .env file.
What's happening:
- GOOGLE_API_KEY authenticates with Google's Gemini models
- COMPOSIO_API_KEY authenticates with Composio
- COMPOSIO_USER_ID identifies the user for session management
```bash
GOOGLE_API_KEY=your-google-api-key
COMPOSIO_API_KEY=your-composio-api-key
COMPOSIO_USER_ID=your-user-id-or-email
```

### 5. Import modules and validate environment

What's happening:
- os reads environment variables
- Composio is the main Composio SDK client
- GoogleProvider declares that you are using Google ADK as the agent runtime
- Agent is the Google ADK LLM agent class
- McpToolset lets the ADK agent call MCP tools over HTTP
```python
import os
import warnings

from composio import Composio
from dotenv import load_dotenv
from google.adk.agents.llm_agent import Agent
from google.adk.tools.mcp_tool.mcp_session_manager import StreamableHTTPConnectionParams
from google.adk.tools.mcp_tool.mcp_toolset import McpToolset

load_dotenv()

warnings.filterwarnings("ignore", message=".*BaseAuthenticatedTool.*")

GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not GOOGLE_API_KEY:
    raise ValueError("GOOGLE_API_KEY is not set in the environment.")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set in the environment.")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set in the environment.")
```

### 6. Create Composio client and Tool Router session

What's happening:
- Authenticates to Composio with your API key
- Declares Google ADK as the provider
- Spins up a short-lived MCP endpoint for your user and selected toolkit
- Stores the MCP HTTP URL for the ADK MCP integration
```python
composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["google_search_console"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url,
print(f"Composio MCP URL: {COMPOSIO_MCP_URL}")
```

### 7. Set up the McpToolset and create the Agent

What's happening:
- Connects the ADK agent to the Composio MCP endpoint through McpToolset
- Uses Gemini as the model powering the agent
- Lists exact tool names in instruction to reduce misnamed tool calls
```python
composio_toolset = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url=COMPOSIO_MCP_URL,
        headers={"x-api-key": COMPOSIO_API_KEY}
    )
)

root_agent = Agent(
    model="gemini-2.5-flash",
    name="composio_agent",
    description="An agent that uses Composio tools to perform actions.",
    instruction=(
        "You are a helpful assistant connected to Composio. "
        "You have the following tools available: "
        "COMPOSIO_SEARCH_TOOLS, COMPOSIO_MULTI_EXECUTE_TOOL, "
        "COMPOSIO_MANAGE_CONNECTIONS, COMPOSIO_REMOTE_BASH_TOOL, COMPOSIO_REMOTE_WORKBENCH. "
        "Use these tools to help users with Google search console operations."
    ),
    tools=[composio_toolset],
)

print("\nAgent setup complete. You can now run this agent directly ;)")
```

### 8. Run the agent

Execute the agent from the project root. The web command opens a web portal where you can chat with the agent.
What's happening:
- adk run runs the agent in CLI mode
- adk web . opens a web UI for interactive testing
```bash
# Run in CLI mode
adk run my_agent

# Or run in web UI mode
adk web
```

## Complete Code

```python
import os
import warnings

from composio import Composio
from composio_google import GoogleProvider
from dotenv import load_dotenv
from google.adk.agents.llm_agent import Agent
from google.adk.tools.mcp_tool.mcp_session_manager import StreamableHTTPConnectionParams
from google.adk.tools.mcp_tool.mcp_toolset import McpToolset

load_dotenv()
warnings.filterwarnings("ignore", message=".*BaseAuthenticatedTool.*")

GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not GOOGLE_API_KEY:
    raise ValueError("GOOGLE_API_KEY is not set in the environment.")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set in the environment.")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set in the environment.")

composio_client = Composio(api_key=COMPOSIO_API_KEY, provider=GoogleProvider())

composio_session = composio_client.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["google_search_console"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url


composio_toolset = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url=COMPOSIO_MCP_URL,
        headers={"x-api-key": COMPOSIO_API_KEY}
    )
)

root_agent = Agent(
    model="gemini-2.5-flash",
    name="composio_agent",
    description="An agent that uses Composio tools to perform actions.",
    instruction=(
        "You are a helpful assistant connected to Composio. "
        "You have the following tools available: "
        "COMPOSIO_SEARCH_TOOLS, COMPOSIO_MULTI_EXECUTE_TOOL, "
        "COMPOSIO_MANAGE_CONNECTIONS, COMPOSIO_REMOTE_BASH_TOOL, COMPOSIO_REMOTE_WORKBENCH. "
        "Use these tools to help users with Google search console operations."
    ),  
    tools=[composio_toolset],
)

print("\nAgent setup complete. You can now run this agent directly ;)")
```

## Conclusion

You've successfully integrated Google search console with the Google ADK through Composio's MCP Tool Router. Your agent can now interact with Google search console using natural language commands.
Key takeaways:
- The Tool Router approach dynamically routes requests to the appropriate Google search console tools
- Environment variables keep your credentials secure and separate from code
- Clear agent instructions reduce tool calling errors
- The ADK web UI provides an interactive interface for testing and development
You can extend this setup by adding more toolkits to the toolkits array in your session configuration.

## How to build Google search console MCP Agent with another framework

- [ChatGPT](https://composio.dev/toolkits/google_search_console/framework/chatgpt)
- [OpenAI Agents SDK](https://composio.dev/toolkits/google_search_console/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/google_search_console/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/google_search_console/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/google_search_console/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/google_search_console/framework/codex)
- [Cursor](https://composio.dev/toolkits/google_search_console/framework/cursor)
- [VS Code](https://composio.dev/toolkits/google_search_console/framework/vscode)
- [OpenCode](https://composio.dev/toolkits/google_search_console/framework/opencode)
- [OpenClaw](https://composio.dev/toolkits/google_search_console/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/google_search_console/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/google_search_console/framework/cli)
- [LangChain](https://composio.dev/toolkits/google_search_console/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/google_search_console/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/google_search_console/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/google_search_console/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/google_search_console/framework/crew-ai)

## Related Toolkits

- [Excel](https://composio.dev/toolkits/excel) - Microsoft Excel is a robust spreadsheet application for organizing, analyzing, and visualizing data. It's the go-to tool for calculations, reporting, and flexible data management.
- [21risk](https://composio.dev/toolkits/_21risk) - 21RISK is a web app built for easy checklist, audit, and compliance management. It streamlines risk processes so teams can focus on what matters.
- [Abstract](https://composio.dev/toolkits/abstract) - Abstract provides a suite of APIs for automating data validation and enrichment tasks. It helps developers streamline workflows and ensure data quality with minimal effort.
- [Addressfinder](https://composio.dev/toolkits/addressfinder) - Addressfinder is a data quality platform for verifying addresses, emails, and phone numbers. It helps you ensure accurate customer and contact data every time.
- [Agenty](https://composio.dev/toolkits/agenty) - Agenty is a web scraping and automation platform for extracting data and automating browser tasks—no coding needed. It streamlines data collection, monitoring, and repetitive online actions.
- [Ambee](https://composio.dev/toolkits/ambee) - Ambee is an environmental data platform providing real-time, hyperlocal APIs for air quality, weather, and pollen. Get precise environmental insights to power smarter decisions in your apps and workflows.
- [Ambient weather](https://composio.dev/toolkits/ambient_weather) - Ambient Weather is a platform for personal weather stations with a robust API for accessing local, real-time, and historical weather data. Get detailed environmental insights directly from your own sensors for smarter apps and automations.
- [Anonyflow](https://composio.dev/toolkits/anonyflow) - Anonyflow is a service for encryption-based data anonymization and secure data sharing. It helps organizations meet GDPR, CCPA, and HIPAA data privacy compliance requirements.
- [Api ninjas](https://composio.dev/toolkits/api_ninjas) - Api ninjas offers 120+ public APIs spanning categories like weather, finance, sports, and more. Developers use it to supercharge apps with real-time data and actionable endpoints.
- [Api sports](https://composio.dev/toolkits/api_sports) - Api sports is a comprehensive sports data platform covering 2,000+ competitions with live scores and 15+ years of stats. Instantly access up-to-date sports information for analysis, apps, or chatbots.
- [Apify](https://composio.dev/toolkits/apify) - Apify is a cloud platform for building, deploying, and managing web scraping and automation tools called Actors. It lets you automate data extraction and workflow tasks at scale—no infrastructure headaches.
- [Autom](https://composio.dev/toolkits/autom) - Autom is a lightning-fast search engine results data platform for Google, Bing, and Brave. Developers use it to access fresh, low-latency SERP data on demand.
- [Beaconchain](https://composio.dev/toolkits/beaconchain) - Beaconchain is a real-time analytics platform for Ethereum 2.0's Beacon Chain. It provides detailed insights into validators, blocks, and overall network performance.
- [Big data cloud](https://composio.dev/toolkits/big_data_cloud) - BigDataCloud provides APIs for geolocation, reverse geocoding, and address validation. Instantly access reliable location intelligence to enhance your applications and workflows.
- [Bigpicture io](https://composio.dev/toolkits/bigpicture_io) - BigPicture.io offers APIs for accessing detailed company and profile data. Instantly enrich your applications with up-to-date insights on 20M+ businesses.
- [Bitquery](https://composio.dev/toolkits/bitquery) - Bitquery is a blockchain data platform offering indexed, real-time, and historical data from 40+ blockchains via GraphQL APIs. Get unified, reliable access to complex on-chain data for analytics, trading, and research.
- [Brightdata](https://composio.dev/toolkits/brightdata) - Brightdata is a leading web data platform offering advanced scraping, SERP APIs, and anti-bot tools. It lets you collect public web data at scale, bypassing blocks and friction.
- [Builtwith](https://composio.dev/toolkits/builtwith) - BuiltWith is a web technology profiler that uncovers the technologies powering any website. Gain actionable insights into analytics, hosting, and content management stacks for smarter research and lead generation.
- [Byteforms](https://composio.dev/toolkits/byteforms) - Byteforms is an all-in-one platform for creating forms, managing submissions, and integrating data. It streamlines workflows by centralizing form data collection and automation.
- [Cabinpanda](https://composio.dev/toolkits/cabinpanda) - Cabinpanda is a data collection platform for building and managing online forms. It helps streamline how you gather, organize, and analyze responses.

## Frequently Asked Questions

### What are the differences in Tool Router MCP and Google search console MCP?

With a standalone Google search console MCP server, the agents and LLMs can only access a fixed set of Google search console tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Google search console and many other apps based on the task at hand, all through a single MCP endpoint.

### Can I use Tool Router MCP with Google ADK?

Yes, you can. Google ADK fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Google search console tools.

### Can I manage the permissions and scopes for Google search console while using Tool Router?

Yes, absolutely. You can configure which Google search console scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

### How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Google search console data and credentials are handled as safely as possible.

---
[See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)