All integrations

Google Search Console integration, MCP and CLI

Use it in the Hyper app or from Claude, ChatGPT and any AI client.

Works with

Tools 7

4 read, 2 write, 1 destructive

Google Search Console operations - list verified sites, manage sitemaps, submit URLs for indexing, and retrieve site performance data

  • Get console performance

    Retrieve search analytics and performance data from Google Search Console for a verified site.

  • Get console sitemaps

    Get detailed information about a specific sitemap including submission date, processing status, errors, and warnings.

  • List console sitemaps

    List all sitemaps for a verified site in Google Search Console.

  • List console sites

    List all verified sites/properties in your Google Search Console account.

  • Submit console sitemaps

    Submit or update a sitemap to Google Search Console.

  • Submit console URLs

    Submit a URL to Google Search Console for indexing.

  • Delete console sitemaps

    Remove a sitemap from Google Search Console.

Frequently asked questions

Hyper MCP serves 7 Google Search Console tools from one endpoint, https://backend.hyperfx.ai/mcp/, next to the other apps you connect to Hyper. Any MCP client can use them, and the Hyper CLI runs the same tools from a terminal.

Connect Google Search Console once in Hyper, under Apps. Every client you add Hyper MCP to then uses that connection.

Claude Code, Claude, ChatGPT, Codex, Cursor and OpenCode, through Hyper MCP. Agents in the Hyper app use the same tools.

Yes. Of its 7 tools, 4 read, 2 write, 1 destructive. Any action can be set to require approval, and Claude asks you before every write or destructive call.

Hyper has a free 7-day trial, then 49 USD/month. See pricing.

Further reading

What is Google Search Console MCP?

Google Search Console MCP is Google Search Console inside Hyper MCP: 7 tools (4 read, 2 write, 1 destructive) on the same endpoint as every other app you connect to Hyper. One endpoint, one sign-in, for any AI app that supports the Model Context Protocol.

Your AI client sees about ten Hyper tools (search, describe, call_read, call_write and a few more) and finds the Google Search Console ones with search. Read tools run without asking; write and destructive tools ask you first in Claude.

What you can do with Google Search Console on Hyper

  • Console sitemap

    Delete, get, list and submit.

How to connect Google Search Console to your AI client

  1. 1. Create a Hyper account

    Free 7-day trial, then 49 USD/month.

  2. 2. Connect Google Search Console in Hyper

    Open Apps and connect it.

  3. 3. Add Hyper MCP to your client

    Paste https://backend.hyperfx.ai/mcp/ as a custom connector or remote MCP server, or run the Claude Code command above.

  4. 4. Ask for Google Search Console

    Your client finds the Google Search Console tools with search and asks before it writes.

Why use Hyper for Google Search Console

  • One endpoint, every app

    Connect once and get Google Search Console with every integration, scraper, generator and platform tool you enabled on Hyper.

  • Bring your existing setup

    Your connections, agents, tasks and skills carry over to every client.

  • Per-tool guardrails

    Turn actions on or off and require approval on each one, in every client.

  • Use Hyper from anywhere

    Claude, ChatGPT, OpenCode, Cursor, Codex and any other MCP client.