Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
EDGEO_DATA_DIRNoSet to choose a different local EdGEO data directory where the Search Console refresh token is stored. Optional.
GEMINI_API_KEYNoGemini 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

CapabilityDetails
tools
{
  "listChanged": true
}
prompts
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
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. 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 renders JavaScript or follows links to other hosts. Reports known queued URL counts, not sitewide coverage.

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-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 substring.

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 edgeo-mcp search-console connect. Reads Search Console directly with OAuth read-only access; AI feature labels are never inferred from generic search rows.

Prompts

Interactive templates invoked by user choice

NameDescription
edgeoAudit 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

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 9 tools

Disambiguation4/5

Most tools occupy clearly distinct slots (crawling, single-page auditing, model querying, Search Console access), and descriptions actively draw boundaries — e.g. analyze_visibility works on supplied answers while query_model produces them, and summarize_search_console vs. compare_visibility_runs differ by input type. The closest pairs are the three Search Console data-entry points (query/search_console_sites/import_csv) and analyze_visibility vs. summarize_search_console, which both digest supplied rows and could be momentarily confused.

Naming Consistency4/5

All names are snake_case under a uniform `edgeo_` prefix with a leading verb, which is predictable and readable. Minor deviation: three tools embed the compound noun `search_console` after the verb, so the verb_noun grammar is less clear there (edgeo_search_console_sites reads as a list operation but has no `list_` verb).

Tool Count5/5

Nine tools sit comfortably in the well-scoped range, and each covers a distinct step (crawl, audit, query, import, query API, summarize, analyze, compare, list properties). No obvious filler or trivially overlapping entries.

Completeness3/5

The surface covers acquisition, analysis, and comparison, but there is no tool to create, persist, or list analysis runs — compare_visibility_runs requires matched completed runs that nothing in this set produces or retrieves, leaving a dead end. There is also no export/report tool to carry findings out, so agents must stitch workflows together externally.

Maintenance

ActivityMaintained
ResponsivenessOutdated data