Google Search Console integration for Model Context Protocol (MCP)
EdGEO 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
Local MCP for evidence-based SEO, GEO, Google AI Search, and Search Console.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user edgeo-mcp '--' npx -y edgeo-mcp
# 2 — ask your agent for something these tools do
# edgeo_audit_page, edgeo_crawl_site, edgeo_analyze_visibility and 6 more
EdGEO costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
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 EdGEO 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 is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user edgeo-mcp '--' npx -y edgeo-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Nothing is required, but it can take GEMINI_API_KEY (Optional Google Gemini API key. Used only when the user explicitly consents to sending a prompt to Gemini.) if you want to set it.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
9 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Fetch and audit one public HTTP/HTTPS HTML page for observable technical SEO and page-structure signals. Does not render JavaScript, measure Core Web Vitals, or verify search indexing.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | Public HTTP or HTTPS page URL to inspect. |
Run a bounded same-host HTML crawl seeded from the start URL and same-host sitemap URLs. Defaults to 50 attempted URLs and accepts up to 200. Preserves trailing slashes when requesting URLs, reads robots.txt first, applies its rules and crawl-delay, separates non-HTML sitemap resources, and never…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | Public HTTP or HTTPS start URL. |
| maxPages | integer | no | Maximum URL fetch attempts, including non-HTML sitemap resources and URL variants that redirect to an already seen page. |
| delayMs | integer | no | — |
Analyze caller-supplied answers with transparent brand alias and citation checks. Keeps prompt types and failures separate; does not call models or automatically label recommendations.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| brandName | string | yes | — |
| aliases | array | no | — |
| brandDomain | string | no | — |
| observations | array | yes | — |
Compare complete answers only when the normalized prompt and recorded source, provider, model, surface, locale, search mode, and prompt type match. Returns paired mention and citation changes with sample counts; does not infer causation or call AI providers.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| brandName | string | yes | — |
| aliases | array | no | — |
| brandDomain | string | no | — |
| before | array | yes | — |
| after | array | yes | — |
Summarize user-supplied Search Console rows by provided feature label, including clicks, impressions, CTR, and impression-weighted average position. Does not connect to Google or infer an AI feature from unlabeled data.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| rows | array | yes | — |
Parse a user-provided CSV or TSV export in memory, recognize common English and Indonesian Search Console headers, and return a transparent summary. The file contents are not uploaded or persisted by this tool.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| csvText | string | yes | — |
| delimiter | string | no | — |
| columnMap | object | no | — |
Send one prompt to a configured local Ollama model or, with explicit consent and GEMINI_API_KEY configured, Google Gemini API. Returns an observation ready for EdGEO visibility analysis. Provider API output is not equivalent to a consumer AI app or Google AI Search result; no citations are assumed.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| provider | string | yes | — |
| model | string | yes | — |
| prompt | string | yes | — |
| locale | string | yes | — |
| promptType | string | yes | — |
| maxOutputTokens | integer | no | — |
| consentToExternalRequest | boolean | no | Must be true to send a prompt to the external Gemini API. Not needed for Ollama loopback. |
List Google Search Console properties for the user's locally authorized Google account. Requires prior setup with edgeo-mcp search-console connect; uses a read-only OAuth scope and returns only properties the Google account can access. Optionally filter property URLs by a case-insensitive…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| siteUrlContains | string | no | Optional case-insensitive substring to filter property URLs. |
Query the user's authorized Google Search Console property for web, image, video, news, Discover, or Google News performance rows. Requires edgeo-mcp search-console connect. Reads Search Console directly with OAuth read-only access; AI feature labels are never inferred from generic search rows.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| siteUrl | string | yes | Verified Search Console property, such as https://example.com/ or sc-domain:example.com. |
| startDate | string | yes | — |
| endDate | string | yes | — |
| dimensions | array | no | — |
| searchType | string | no | — |
| aggregationType | string | no | — |
| rowLimit | integer | no | — |
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under Apache-2.0
- 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 EdGEO 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 | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| 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 (9 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>".
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. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| edgeo_audit_page | untrusted-input | untrusted-input: keyword "fetch", declares openWorldHint: true (interacts with entities outside the server) |
| edgeo_crawl_site | untrusted-input | untrusted-input: keyword "crawl", declares openWorldHint: true (interacts with entities outside the server) |
| edgeo_analyze_visibility | no tags | |
| edgeo_compare_visibility_runs | no tags | |
| edgeo_summarize_search_console | no tags | |
| edgeo_import_search_console_csv | no tags | |
| edgeo_query_model | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| edgeo_search_console_sites | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| edgeo_search_console_query | 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.1.4. Pin a release below and the command asks for exactly that one.
- Adds optional filtering for Search Console properties and gives every MCP tool an explicit input schema.
- More accurate site crawls, a larger page cap, safer agent configuration upgrades, and automatic checks for newer releases.
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 EdGEO 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.