Google Search Console integration for Model Context Protocol (MCP)
Google Search Console is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Google Search Console MCP for analytics, indexing, sitemaps, and SEO diagnostics.
Quickstart
This package runs as a local HTTP server (Streamable HTTP), not over stdio, so a client cannot start it as a process. Start it in a terminal with npx -y @digestseo/mcp-gsc and keep it running, then add the address it listens on to your client as a remote server; that address is not recorded here, so there is no entry to copy.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Google Search Console as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
This package runs as a local HTTP server (Streamable HTTP), not over stdio, so a client cannot start it as a process. Start it in a terminal with npx -y @digestseo/mcp-gsc and keep it running, then add the address it listens on to your client as a remote server; that address is not recorded here, so there is no entry to copy.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
List every tool this server exposes, its configured access mode, and local Google credential state. Call this first if you're unsure what tools are available, whether the deployment is read-only, or whether stored Google credentials are configured. auth_status='connected' means a stored refresh…
No parameter schema on file.
List the Google Search Console properties (sites) the connected Google account has access to. Each entry preserves Google's siteUrl and permissionLevel, derives verification_state plus owner from Google's documented permission levels, and adds api_identifier_kind plus mcp_site_url_accepted. Treat…
No parameter schema on file.
Retrieve one exact Google Search Console property and its connected-account access state. The response preserves Google's permissionLevel and derives verification_state plus owner so callers can distinguish an unverified property and recognize owner-only Indexing API prerequisites without listing…
No parameter schema on file.
Inspect the version of a single URL currently known in Google's index. Returns a conservative normalized index-status summary alongside Google's raw index-status analysis, last crawl, page-fetch/indexing state, canonicals, and rich-results/AMP analysis where available. This API does not test the…
No parameter schema on file.
Inspect the versions of up to 10 URLs currently known in Google's index from one Search Console property. Each successful item includes a conservative normalized index-status summary alongside Google's raw response. This API does not run live URL tests. Google still processes one URL Inspection…
No parameter schema on file.
List sitemaps submitted for a Search Console property. Optionally filter to entries included by one sitemap index. Returns sitemap URLs, provider-reported submission/download timestamps, submitted URL counts, warning and error counts, and sitemap status. lastSubmitted is when the sitemap was…
No parameter schema on file.
No parameter schema on file.
For one exact page URL within the supplied Search Console property, return the queries that produced impressions for it over a date range. This wraps an exact page dimension filter so agents do not need to construct analytics.query filter groups manually. Exact page matching is case-sensitive in…
No parameter schema on file.
For one exact search query, return the site pages that received impressions for it over a date range. This wraps an exact query dimension filter so agents do not need to construct analytics.query filter groups manually. Exact query matching is case-sensitive in Search Console. Use row_limit and…
No parameter schema on file.
Add a website property to the connected Google account's Search Console site set. This does not verify ownership. Domain properties require an sc-domain prefix (e.g., sc-domain:example.com); URL-prefix properties require a full URL (e.g., https://example.com/).
No parameter schema on file.
Remove an existing website property from the connected Google account's Search Console site set. Google documents this operation as removing the site from the user's Search Console sites; it does not delete website content.
No parameter schema on file.
Submit a sitemap URL to a Search Console property. A successful API response means the Search Console submission request succeeded; it does not prove sitemap processing completed or that any page was indexed.
No parameter schema on file.
Remove a submitted sitemap from a Search Console property. This removes the Search Console sitemap entry; it does not delete the remotely hosted sitemap file or prove that any page was deindexed.
No parameter schema on file.
Get status and details of a single sitemap submitted to Google Search Console. lastSubmitted is when the sitemap was submitted to Search Console; lastDownloaded is when Google last downloaded the sitemap. Neither timestamp is a sitemap-file modification time or a page crawl/indexing time.
No parameter schema on file.
Find observed query/page Search Analytics rows with at least the requested impressions whose average position falls in a configurable opportunity range (8-20 by default). Average position is an aggregate Search Console metric, not a literal current rank; CTR is returned for context and is not an…
No parameter schema on file.
Analyze query/page Search Analytics to find queries split across multiple pages. Candidates are ranked deterministically by the observed query/page impression sum, each candidate bounds its page list, and limit/start_row plus result_page provide safe pagination. total_clicks, total_impressions,…
No parameter schema on file.
Assess page-level click declines across two contiguous periods without treating every small click change as content decay. Only pages returned in both Search Analytics period responses are compared; a page missing from one response is not treated as zero because Google does not guarantee every…
No parameter schema on file.
Read the latest successful Indexing API URL_UPDATED and URL_DELETED notifications Google received for a previously submitted URL within an owner-level Search Console property accessible to the connected Google account. This is a read-only notification-receipt lookup, not an index-coverage report…
No parameter schema on file.
Requests indexing through Google's Indexing API for a URL within an owner-level Search Console property accessible to the connected Google account. Google currently restricts this API to pages containing JobPosting structured data or livestream pages containing BroadcastEvent inside VideoObject.…
No parameter schema on file.
Requests a URL_DELETED notification through Google's Indexing API for a URL within an owner-level Search Console property accessible to the connected Google account. Use only for pages that were eligible for the restricted Indexing API (JobPosting or livestream BroadcastEvent in VideoObject).…
No parameter schema on file.
List pages that produced Search Console impressions in the requested period. This is performance data, not an index-coverage inventory: a URL can be indexed even when it is absent here, and Search Analytics can omit some page-level detail. Use urls.inspect or urls.inspect_many for URL-level index…
No parameter schema on file.
Compare Search Console performance metrics (clicks, impressions, CTR, average position) between two distinct date ranges (Period A vs Period B) for a selected dimension (query, page, country, device). Only dimension keys returned in both Search Analytics period responses are compared; a key…
No parameter schema on file.
Generate a plain-language weekly SEO report for one Google Search Console property. Returns a markdown digest covering the 7 days ending on end_date, with week-over-week comparison, top pages, queries gaining or losing traction, and one specific action item. Defaults end_date to 3 days ago so the…
No parameter schema on file.
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Google Search Console or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tools were statically extracted from the published source (23 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
4 of the 23 recovered tools are registered only when accessMode === 'readwrite' holds (src/index.ts:1661) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes only the other 16.
3 of the 23 recovered tools are registered only when accessMode === 'readwrite' holds (src/index.ts:1981) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes only the other 16.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
16 tools are registered unconditionally · (1) 4 more only when accessMode === 'readwrite' holds (src/index.ts:1661) · (2) 3 more only when accessMode === 'readwrite' holds (src/index.ts:1981) — typically when a key or option is configured. All 23 are in the table below and were analysed; the conditional ones are marked.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| server.capabilities | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| sites.list | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| sites.get | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| urls.inspect | untrusted-input | untrusted-input: keyword "fetch", declares openWorldHint: true (interacts with entities outside the server) |
| urls.inspect_many | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| sitemaps.list | untrusted-input | untrusted-input: keyword "crawl", declares openWorldHint: true (interacts with entities outside the server) |
| analytics.query | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| insights.page_queries | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| insights.query_pages | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| sites.add conditional (1) | no tags | |
| sites.delete conditional (1) | no tags | |
| sitemaps.submit conditional (1) | no tags | |
| sitemaps.delete conditional (1) | no tags | |
| sitemaps.get | untrusted-input | untrusted-input: keyword "crawl", declares openWorldHint: true (interacts with entities outside the server) |
| insights.quick_wins | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| insights.cannibalization | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| insights.content_decay | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| indexing.status conditional (2) | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| indexing.request conditional (2) | no tags | |
| indexing.remove conditional (2) | no tags | |
| indexing.list_pages | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| analytics.compare | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| reports.weekly_digest | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.4.36. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
No release note was published with this version.
No release note was published with this version.
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Google Search Console can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.