4,500+ servers built on MCP Fusion
Vinkius

Search Console MCP. Audit site health and query performance data.

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

Google Search Console MCP on Cursor AI Code Editor MCP Client Google Search Console MCP on Claude Desktop App MCP Integration Google Search Console MCP on OpenAI Agents SDK MCP Compatible Google Search Console MCP on Visual Studio Code MCP Extension Client Google Search Console MCP on GitHub Copilot AI Agent MCP Integration Google Search Console MCP on Google Gemini AI MCP Integration Google Search Console MCP on Lovable AI Development MCP Client Google Search Console MCP on Mistral AI Agents MCP Compatible Google Search Console MCP on Amazon AWS Bedrock MCP Support

Just plug in your AI agents and start using Vinkius.

Google Search Console connects your AI client to your site's technical SEO data. You query search traffic, check specific URLs for indexing errors, and manage sitemaps directly.

It handles all site management—from listing properties to submitting new sitemaps—so you don't have to wrestle with the console UI.

What your AI agents can do

Add site

Adds a new website property to your Search Console account.

Delete site

Removes an entire website property from your Search Console account.

Delete sitemap

Deletes a previously submitted sitemap from your records.

+ 7 more capabilities included
Analyze Search Performance

Retrieve search traffic data (clicks, impressions, CTR, position) based on specific filters like date range, country, or device.

Validate URL Index Status

Check if a specific URL is indexed by Google and identify immediate mobile or technical usability errors.

Manage Site Properties

List, retrieve details for, and add or remove entire websites (properties) from your Search Console account.

Review and Submit Sitemaps

List all existing sitemaps for a site, get details on a specific sitemap, and submit new ones directly.

Supported MCP Clients

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
+ other MCP clients
Free for Subscribers

Waiting for input…

AI Agent

Google Search Console MCP Server: 10 Tools for Technical SEO

Manage site indexing, sitemap submission, and URL inspection by calling these 10 specialized tools through your AI client.

add019d75a9

add site

Adds a new website property to your Search Console account.

delete019d75a9

delete site

Removes an entire website property from your Search Console account.

delete019d75a9

delete sitemap

Deletes a previously submitted sitemap from your records.

get019d75a9

get site

Retrieves specific details about a known website property.

get019d75a9

get sitemap

Gets detailed information about a specific, known sitemap.

inspect019d75a9

inspect url

Checks the current index status and mobile usability of any specific URL.

list019d75a9

list sitemaps

Lists all sitemaps that have been submitted for a given site.

list019d75a9

list sites

Lists every verified website property connected to your Search Console account.

query019d75a9

query search analytics

Runs a query against your site's search traffic data (clicks, impressions, etc.).

submit019d75a9

submit sitemap

Submits a new sitemap URL to Google Search Console for processing.

Choose How to Get Started

Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.

Build Your Own

Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.

  • Import from OpenAPI, Swagger, or YAML specs
  • Create Agent Skills with progressive disclosure
  • Deploy to edge with MCPFusion framework
  • Built in DLP, auth, and compliance on every call
  • Real time usage dashboard and cost metering
  • Publish to catalog or keep private
Start building

Make Your AI Do More

Start with Google Search Console, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.

  • Use this MCP plus 4,700+ others, all in one place
  • Add new capabilities to your AI anytime you want
  • Every connection is secured and compliant automatically
  • Track usage and costs across all your servers
  • Works with Claude, ChatGPT, Cursor, and more
  • New servers added to the catalog every week

What you can do with this MCP connector

Google Search Console connects your AI client to your site's technical SEO data. You can query search traffic, check specific URLs for indexing errors, and manage sitemaps right from your agent. It handles all site management—from listing properties to submitting new sitemaps—so you don't have to wrestle with the console UI.

Analyze Search Performance

  • You can run a query against your site's search traffic data using query_search_analytics, letting you check clicks, impressions, CTR, and position. You filter this data by date range, country, or device.

Validate URL Index Status

  • Use inspect_url to check a specific URL's current index status and mobile usability. This tool shows you immediate technical or mobile usability errors for any given page.

Manage Site Properties

  • To see every site property you've verified, run list_sites. You can also get specific details about a known site property using get_site. Need to add a new property? Use add_site. If you're done with a site, delete_site removes the entire property from your Search Console account.

Review and Submit Sitemaps

  • Check all the sitemaps you've submitted for a site by running list_sitemaps. You can get detailed information on a specific sitemap using get_sitemap. Need to send a new sitemap to Google? Use submit_sitemap to submit a new URL for processing. Finally, if a sitemap is bad, delete_sitemap takes it out of your records.

How Search Console MCP Works

  1. 1 Subscribe to the server and provide your Google OAuth Client ID and Secret.
  2. 2 Complete the secure Google authorization flow to link your account.
  3. 3 Start by telling your AI agent what you need—e.g., 'What were the top 5 queries last week?'—and it runs the necessary tools.

The bottom line is your AI agent handles the complex Google Search Console API calls so you can talk to your SEO data naturally.

Who Is Search Console MCP For?

The SEO Specialist who needs to audit a new launch before the client sees it. The Web Developer who needs to automate sitemap checks during deployment. The Content Marketer who needs to know which keywords are actually driving traffic to the blog. It's for anyone whose job depends on accurate, current site visibility.

SEO Specialist

Pulls search query data for specific landing pages or verifies if a recently launched page is indexed.

Web Developer

Automates URL inspections during deployments and ensures sitemaps process correctly before launch.

Content Marketer

Finds out what keywords are driving traffic to blog posts through simple conversational queries.

What Changes When You Connect

  • Query specific data points—like clicks, impressions, or CTR—using query_search_analytics instead of building complex spreadsheet filters. You just ask for the data you need.
  • Automate URL checks. Use inspect_url to verify if a new article is indexed and if Google sees any mobile errors, all without navigating the console.
  • Manage your entire site portfolio. Use list_sites to see all connected properties, or add_site to get a new domain under surveillance.
  • Simplify sitemap submission. Instead of copying and pasting, use submit_sitemap to push a new XML file directly from your chat.
  • Streamline site cleanup. Use list_sitemaps and delete_sitemap to keep your sitemap records clean and accurate.
  • Get site context instantly. Use get_site to pull up essential metadata for a specific property without having to navigate to its main page.

Real-World Use Cases

01

Checking a new landing page launch.

The developer finishes a new landing page and needs to know if Google saw it. They tell their agent to run inspect_url on the specific URL. The agent reports back: 'Indexed, mobile usability is Pass.' Problem solved in seconds.

02

Auditing last month's keyword performance.

The content marketer wants to know which keywords drove the most traffic last month. They ask the agent to run query_search_analytics for 'best coffee' and get a breakdown of clicks and impressions. They immediately identify a weak keyword to target.

03

Maintaining site structure after a move.

The ops engineer moves the site to a new domain and needs to update the sitemaps. They use list_sites to confirm the old site is removed, then run add_site and submit_sitemap with the new XML file. The site is re-indexed correctly.

04

Cleaning up old, unused sitemaps.

The SEO specialist finds old, redundant sitemaps slowing down the process. They run list_sitemaps to see the list, identify the stale one, and use delete_sitemap to clean up the records.

The Tradeoffs

Manual dashboard clicking

Opening the Search Console UI, clicking 'Performance', setting date ranges, filtering by device, and manually copying the top 5 queries into a spreadsheet.

Just ask your agent: 'What were the top 5 search queries last week?' The agent runs query_search_analytics and gives you the data structure immediately.

Assuming index status

Writing content and assuming the URL is indexed because it's on the site. You spend days waiting for Google to catch up.

Always run inspect_url immediately after publishing. It confirms the index status and flags any mobile usability issues before the traffic hits.

Over-submitting sitemaps

Manually submitting a sitemap every time a single image changes, leading to unnecessary processing queues.

Use list_sitemaps to check if a sitemap exists, and then use submit_sitemap only when the structural content has fundamentally changed.

When It Fits, When It Doesn't

Use this server if you need to programmatically manage the technical SEO lifecycle. You need to query data sets (like query_search_analytics) or perform validation checks (like inspect_url) against a live, external source. Don't use this if you just need general marketing advice or competitor research—you'll need a different tool for that. If your goal is simply to check a few URLs, inspect_url is the fastest way. If you need to manage the whole site structure, use list_sites and submit_sitemap together.

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Google Search Console. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

VINKIUS INFRASTRUCTURE

Cloud Hosted

Managed infra

V8 Isolated

Sandboxed per request

Zero-Trust Proxy

No stored credentials

DLP Enforced

Policy on every call

GDPR Compliant

EU data residency

Token Compression

~60% cost reduction

How we secure it →

Works with Claude, ChatGPT, Cursor, and more

The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.

This server provides 10 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.

Available Capabilities

add_site delete_site delete_sitemap get_site get_sitemap inspect_url list_sitemaps list_sites query_search_analytics submit_sitemap

Sifting through the Search Console UI is a time sink.

Today, checking your site's performance means logging into the Search Console, clicking through multiple tabs—Performance, Indexing, Enhancements—and manually setting date ranges and filters. You end up cross-referencing data points across five different screens just to answer a simple question about a keyword.

With the Google Search Console MCP Server, you talk to your agent. You ask, 'What were the top 5 queries last week?' and it runs `query_search_analytics`. You get the structured, clean data right in the chat. No clicks, no wasted time.

Google Search Console MCP Server: Manage site indexing and performance.

Gone are the days of manually checking every sitemap version or having to remember the exact site ID. You can use `list_sites` to see every property and `list_sitemaps` to check the status of every sitemap in one place.

Your agent treats the entire site structure like a database. It manages the properties and sitemaps for you. You just tell it what needs to change.

Common Questions About Search Console MCP

How do I check if a URL is indexed using the Google Search Console MCP Server? +

Use the inspect_url tool. It checks the index status and mobile usability of a specific URL. The response tells you if the page is live in Google's search results.

Can I use query_search_analytics to get data for multiple countries? +

Yes, you can specify multiple countries in the query. You'll get a breakdown of clicks, impressions, and CTR for each location you list.

What is the difference between list_sites and get_site? +

Use list_sites to see all properties connected to your account. Use get_site if you already know the exact site ID and just need its specific details.

How do I submit a new sitemap using the submit_sitemap tool? +

Simply provide the full URL of your sitemap to the agent. The submit_sitemap tool handles the submission and confirms the status for Googlebot.

How do I manage my web properties using the `list_sites` and `add_site` tools? +

Use list_sites to view all your verified properties in one go. You then use add_site to onboard new domains into the server's scope.

What should I do if I encounter an indexing error when I run `inspect_url`? +

If inspect_url finds an error, the tool details the problem (e.g., 'Noindex' tag). You then fix the source code on your end and re-run the inspection.

Can I check the status of a specific sitemap using the `get_sitemap` tool? +

Yes, get_sitemap retrieves specific metadata for a sitemap. You need the sitemap's URL or ID to run this check.

Is there a limit to how often I can run `query_search_analytics`? +

The rate limits are governed by the Google API quota you connect with. Check your Google Cloud console for current usage caps.

Can I check why a specific page isn't appearing in Google? +

Yes. Use the inspect_url tool to run a live inspection on the URL. The AI will return the index status and highlight any errors, such as 'Noindex detected' or mobile usability issues.

How do I find out my top performing keywords? +

You can ask the AI to query_search_analytics with the dimension set to 'query'. It will return your top keywords based on clicks and impressions for the requested date range.

Can I submit a new XML sitemap through this integration? +

Absolutely! Use the submit_sitemap tool, provide your site URL and the path to your sitemap (e.g., 'https://example.com/sitemap.xml'). Google will schedule it for processing.

More in this category

You might also like

Built & Managed by Vinkius 30s setup 10 tools

We've already built the connector for Search Console. Just plug in your AI agents and start using Vinkius.

No hosting. No infrastructure. No complex setup.
All 10 tools are live and waiting. You're up and running in seconds.

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
+ other MCP clients

Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.

Zero hosting required Full MCP catalog included Enterprise-grade security Auto-updated by Vinkius

Built, hosted, and secured by Vinkius. You just connect and go.