Google Search Console MCP server

Read from the package source without running it. The installed server may list more.

• add_site

  Adds a website to your Search Console account, enabling you to monitor and manage its search performance.

• delete_sitewrite action

  Removes a website property from your Search Console account, preventing further monitoring and analysis of that site.

• delete_sitemapwrite action

  Removes a sitemap from the Sitemaps report. Note that this action does not prevent Google from crawling the sitemap or previously indexed URLs from that sitemap.

• get_site

  Retrieves detailed information about a specific site property registered in Google Search Console, including its configuration and metadata.

• get_sitemap

  Retrieves detailed information about a specific sitemap for a website, including its status and metadata.

• inspect_url_index_status

  Inspect the indexing status of a specific URL within a Search Console property. Returns detailed information about whether the URL is indexed and any associated issues.

• list_sitemaps

  Retrieves all sitemaps submitted for a website or included in a sitemap index file. Use this to view the complete list of sitemaps Google has discovered for your site.

• list_sites

  Retrieves a list of all Search Console sites that the authenticated user has access to. This includes both verified and unverified properties.

• query_search_analytics

  Query Google Search Console analytics data with custom filters and grouping. Returns aggregated performance metrics (clicks, impressions, CTR, position) for your specified dimensions and date range.

• submit_sitemapwrite action

  Submits a sitemap to Google Search Console for a specified site. This enables Google to discover and index the URLs listed in your sitemap.

• test_mobile_friendly

  Tests whether a given URL is mobile-friendly by analyzing its mobile rendering and usability. Optionally returns a screenshot of the mobile view.

• Code scan5 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitylocal package, no credentials required12/15
• Maintenancelast push 138 days ago8/15
• Maintainer identityregistry namespace matches repository owner7/10

Safety score

80/100

higher than 60% of 769 SEO servers

Tools

11

the typical SEO server has 6

Tools that change things

27%

typical: 0%. Fewer write tools means less an agent can break

GitHub stars

31

more than 95% of 405 SEO servers

Google Search Console: common questions

Is Google Search Console MCP server safe?

Mostly: it is graded B (80/100). Read the Google Search Console safety report

How do I install Google Search Console?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Google Search Console need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Google Search Console maintained?

The last commit was 176 days ago (2026-05-12). The latest release is v1.0.3.

What can I use instead of Google Search Console?

Servers from other publishers that do the same job: SEO Skill MCP server, Google Ads + Meta Ads + SEO/GEO MCP server and SEO Tools: Google Search Console MCP server.

How does Google Search Console compare with other SEO MCP servers?

safety score 80/100 (higher than 60% of 769 SEO servers); tools 11 (the typical SEO server has 6); tools that change things 27% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.