How to integrate Google search console MCP with OpenCode

Trusted by teams at
AWS
Glean
Zoom
Airtable
GET STARTED FOR FREEGET A DEMO

30 min · no commitment · see it on your stack

Google search console logo
OpenCode logo
divider

How to integrate Google search console MCP with OpenCode

This guide explains how to connect Google search console MCP to OpenCode using Composio Connect, which simplifies OAuth, API changes, and reliability concerns.

There are two ways to set this up:

Also integrate Google search console with

Why use Composio?

Composio provides a single MCP server or CLI tool that exposes a set of meta-tools, allowing you to:

  • Connect to 1,000+ apps with on-demand tool loading, so you do not fill your LLM context window with unnecessary tool definitions.
  • Use programmatic tool calling through a remote Bash tool, letting LLMs write their own code to handle complex tool chaining. This reduces back-and-forth for frequent tool calls.
  • Handle large tool responses outside the LLM context to keep conversations lean.

Connect Google search console with OpenCode

Option 1: Using Composio CLI

1. Install Composio CLI

Install the Composio CLI, authenticate, and initialize your project:

bash
# Install the Composio CLI
curl -fsSL https://composio.dev/install | bash

# Authenticate with Composio
composio login

During login, you will be redirected to the sign-in page. Finish the flow and you are all set.

Composio CLI authorization screen

2. Authorize Google search console

Once the CLI is installed, it is essentially done. Give OpenCode access to your apps with these steps:

  1. Launch OpenCode.
  2. Prompt it to "Authenticate with Google search console Composio".
  3. Complete the authentication and authorization flow, and your Google search console integration is all set.
  4. Start asking anything you want.

Option 2: Using Composio MCP

You can also connect Google search console to OpenCode by adding Composio as an MCP server through the OpenCode CLI.

1. Add the Composio MCP server

bash
opencode mcp add

This launches an interactive prompt.

2. Fill in the fields

FieldValue
Namecomposio
Typeremote
URLhttps://connect.composio.dev/mcp
Require OAuthYes
Have client IDNo
OpenCode MCP server interactive prompt for Composio

Alternatively, you can skip the interactive prompt and paste the configuration directly into your OpenCode config file.

Open your global OpenCode config:

bash
open ~/.config/opencode/opencode.json

Add this under the mcp key and save the file.

bash
{
  "mcp": {
    "composio": {
      "type": "remote",
      "url": "https://connect.composio.dev/mcp",
      "enabled": true
    }
  }
}

3. Authenticate

Authenticate the Composio MCP server you just added:

bash
opencode mcp auth composio

This opens a browser session. Authorize Composio and you are done.

Composio browser authorization for OpenCode MCP

4. Verify installation

bash
opencode mcp list

5. Connect Google search console with OpenCode

Now, in the chat, ask the agent to connect to Google search console or give it any Google search console-related task.

For example, ask it to:

  • "Fetch last week's top search queries"
  • "Inspect indexing status for this URL"
  • "List all sitemaps for your site"

It will prompt you to authenticate and authorize access to Google search console.

That is it. Composio tools are now available in OpenCode, and your Google search console account is ready to use.

Supported Tools & Triggers

Tools
Get SitemapRetrieves information about a specific sitemap for a site.
Inspect URLInspects a url for indexing issues and status in google search console.
List SitemapsLists all sitemaps for a site in google search console.
List SitesLists all sites owned by the authenticated user in google search console.
Search Analytics QueryQueries google search console for search analytics data including clicks, impressions, ctr, and position metrics.
Submit SitemapSubmits a sitemap to google search console for indexing.

Way Forward

Now that Google search console is connected, extend your setup by connecting the other apps you already use every day, so your agent can run true cross-app workflows end to end.

  • Connect Calendar to turn threads into scheduled meetings automatically.
  • Connect Slack or Teams to post summaries, approvals, and alerts where your team works.
  • Connect Notion, Linear, Jira, or Asana to convert requests into tickets, tasks, and docs.
  • Connect Drive, Dropbox, or OneDrive to fetch, file, and share attachments without manual steps.

Start with one workflow you do repeatedly, then keep adding apps as you find new handoffs. With everything behind a single MCP endpoint, your agent can coordinate multiple tools safely and reliably in one conversation.

How to build Google search console MCP Agent with another framework

ChatGPT logo

ChatGPT

Use Google search console MCP with ChatGPT

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Google search console MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Google search console MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Google search console MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Google search console MCP with Claude Cowork

Codex logo

Codex

Use Google search console MCP with Codex

Cursor logo

Cursor

Use Google search console MCP with Cursor

OpenClaw logo

OpenClaw

Use Google search console MCP with OpenClaw

Hermes logo

Hermes

Use Google search console MCP with Hermes

CLI logo

CLI

Use Google search console MCP with CLI

Google ADK logo

Google ADK

Use Google search console MCP with Google ADK

LangChain logo

LangChain

Use Google search console MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Google search console MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Google search console MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Google search console MCP with LlamaIndex

CrewAI logo

CrewAI

Use Google search console MCP with CrewAI

VS Code logo

VS Code

Use Google search console MCP with VS Code

FAQ

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 OpenCode?

Yes, you can. OpenCode 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.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.

Get started for freeGet a demo↗