EdGEO
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EDGEO_DATA_DIR | No | Set to choose a different local EdGEO data directory where the Search Console refresh token is stored. Optional. | |
| GEMINI_API_KEY | No | Gemini API key, configured in the MCP process environment. The Gemini tool requires `consentToExternalRequest: true` before sending a prompt. Optional; only needed to use the Gemini API connector. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| edgeo_audit_pageA | 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. |
| edgeo_crawl_siteA | Run a bounded same-host HTML crawl seeded from the start URL and same-host sitemap URLs. Reads robots.txt first, applies its rules and crawl-delay, and never renders JavaScript or follows links to other hosts. |
| edgeo_analyze_visibilityA | 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. |
| edgeo_compare_visibility_runsB | 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. |
| edgeo_summarize_search_consoleA | 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. |
| edgeo_import_search_console_csvA | 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. |
| edgeo_query_modelB | 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. |
| edgeo_search_console_sitesA | List Google Search Console properties for the user's locally authorized Google account. Requires prior setup with |
| edgeo_search_console_queryB | Query the user's authorized Google Search Console property for web, image, video, news, Discover, or Google News performance rows. Requires |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| edgeo | Audit a website or supplied/authorized SEO, GEO, and Search Console evidence using EdGEO tools and an evidence-first report. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool has a distinct action and input source: crawling a site, auditing one page, querying a model, analyzing supplied answers, comparing runs, and four separate Search Console operations. The descriptions explicitly delineate boundaries and non-goals, so an agent should be able to select tools reliably.
All tool names use the edgeo_ prefix and snake_case, and most follow an action_object pattern. Minor deviations appear in the Search Console tools, where the domain is embedded before the object or where query appears at the end rather than in a clean verb_noun form.
Nine tools is well within the appropriate range for a focused SEO/AI visibility and Search Console server. Each tool appears to earn its place without obvious redundancy.
The set covers crawl, page audit, model querying, visibility analysis, run comparison, and Search Console listing/querying/importing/summarizing. Minor gaps exist, such as report export, index verification, or model/provider discovery, but core workflows are represented.