Subscriber OAuth
Connect a Google account per MCP subscriber, check connection state, and disconnect stored Search Console access when needed.
Google Search Console MCP Application
Use your Search Console data inside your AI assistant
This application connects a user's own Google Search Console account to an MCP-compatible AI assistant. Its purpose is to help website owners, SEO professionals, and developers analyze search performance, inspect URL indexing, view verified properties, and manage sitemaps from the assistant they already use.
Find content opportunities faster
Check index status instantly
Fix sitemap issues with evidence
Application purpose
A secure bridge between Google Search Console and MCP clients
After a user authorizes Google access, the app makes Search Console tools available only within that user's connected MCP workflow.
- What users can do
- Query clicks, impressions, CTR, and position; inspect URL index status; list Search Console properties; and review or manage sitemaps.
- Why Google access is required
- The app needs the Search Console scope to retrieve the user's property data and perform property or sitemap actions that the user requests.
- How access is controlled
- Access is tied to the connected user, the account can be disconnected, and destructive property or sitemap actions require explicit confirmation.
Choose your AI app
Quick setup
codex mcp add gsc-mcp --url https://google-search-console-mcp-server.mcpize.run/mcp
One connection gives your AI assistant live Search Console data for SEO research, diagnostics, and action planning.
POST /mcp
live transport
query_search_analytics
412 ms
148,392
clicks
3.4M
impressions
4.36%
CTR
8.7
avg pos.
- google search console api mcp+31%
- url inspection automation+18%
- sitemap submission workflow+12%
connect_google_account
list_sites
inspect_url
submit_sitemap
Why it exists
Search data belongs in the same loop as the work.
SEO and product teams keep bouncing between Search Console exports, browser tabs, spreadsheets, and agent prompts. This server exposes the core Search Console API through MCP so an assistant can check evidence before recommending titles, canonicals, sitemap changes, or page priorities.
Tool surface
Built around the operations you actually run.
Performance queries
Query Search Analytics with dimensions, filters, data state, pagination, search type, and aggregation controls.
URL inspection
Inspect Google index status for a URL inside a verified Search Console property, with optional language targeting.
Submit and manage
List, fetch, submit, and delete sitemaps from the same assistant session that diagnoses crawl or indexing issues.
Connection flow
Add the server, authorize once, then work from live data.
Pick a client
Choose the MCP client you actually work in, from terminal agents to hosted web apps.
Add through MCPize
Use the hosted listing or the one-line add command to register the hosted server with that client.
Authorize Google
The server returns a Google OAuth URL and stores refresh access per subscriber after the callback.
Ask with evidence
Agents can list properties, query performance, inspect URLs, and manage sitemap state from the MCP tool surface.
FAQ
Answers for search, indexing, and setup intent.
What does the Google Search Console MCP Server do?
It connects Search Console properties to MCP clients so agents can query performance data, inspect URLs, list properties, and manage sitemaps from the same workflow.
Does it require a local MCP server setup?
No. Add the hosted server to a supported MCP client through MCPize, authorize Google, and use the tools from there.
Which Search Console operations are supported?
The tool surface includes Google account connection, site listing, Search Analytics queries, URL Inspection, and sitemap list, fetch, submit, and delete operations.
How are write actions protected?
Mutation-style operations use explicit safety rails and confirmation guards so agents can inspect evidence before changing sitemap state.
Ready as MCP