GEO Tracker by DigestSEO

DigestSEO — AI Visibility MCP for SEO & GEO

See your first result

mcp-geo is a free, self-hostable MCP server for measuring brand mentions and, where providers return them, source citations across supported AI answer surfaces. It helps SEO practitioners and agencies compare observations by engine and inspect the underlying evidence. A scan is a point-in-time sample, not a guaranteed ranking or citation outcome.

*Open the full example report · How the methodology works*. This is an example report generated through the MCP tools, not a customer testimonial or a promised result.

Your first local scan, after connecting the stdio MCP server:

1. Track: ask your MCP client to run track_brand with your own brand_id, name, domain, and ideally a precise category. By default it creates three provider-free category-anchored starter questions, not a validated measurement sample. Without a category, its brand-name placeholders can bias scores: replace those prompts before scanning.
2. Measure: after reviewing and, when needed, replacing the starter questions with representative independent buyer prompts, run refresh_brand with that brand_id. Live scans use your provider API keys and may incur charges. Engines without keys are skipped; Google AI Mode requires a separate explicit opt-in. Retrying after a partial scan makes fresh provider requests for all active prompts on the selected engines, including ones that previously succeeded; old successful answers are not reused as new evidence. Review partial coverage with check_visibility before choosing whether and when to retry.
3. Inspect: run check_visibility with the same brand_id to view available per-engine scores and evidence. Use get_citations to inspect citation records where providers supply sources.

Winning prompts now distinguish engines_mentioned_in (brand named in the answer) from engines_with_brand_link (the answer or provider sources included a brand-domain link). The older engines_cited_in field is retained for compatibility but counts mentions, not verified citations. A linked source alone is not scored as an answer mention.

check_visibility.prompt_set_comparability warns when the latest scored observations include prompts no longer in the active prompt set, such as after replacing buyer-intent questions. Its engines_with_retired_prompt_evidence identifies affected engines without rewriting historical measurements. Missing or failed answers are handled separately by per-engine coverage, not misclassified as retired prompts. Rerun the affected engines when a current-prompt comparison is needed; this uses your configured providers and may incur charges.

check_visibility.configuration_comparability separately identifies engines whose latest scans started before the tracked brand's most recent settings update. Historical scores are not silently recomputed under a new domain, name, alias, exclusion, or competitor list. This is a conservative warning: the database does not retain which settings changed, so a refresh-cadence-only edit can also trigger it. Review the change before interpreting old scores as current-brand evidence; rescanning uses your provider keys and may incur charges.

Choose your setup: Quick Install and client-specific instructions for local MCP hosts · Getting Started for provider keys and optional Cloudflare hosting · What the report contains · Privacy. Hosted remote MCP deployments manage brands through their protected admin routes rather than local track_brand.

Quick Install

Runs locally over stdio with your own API keys. Brands, scan history, and cached responses are stored on your machine; scan prompts are sent to the AI providers you configure (see Privacy Policy). Set at least one engine key (OPENAI_API_KEY, ANTHROPIC_API_KEY, GEMINI_API_KEY, PERPLEXITY_API_KEY, XAI_API_KEY, SERPAPI_API_KEY); engines without a key skip gracefully.

Runtime: Node.js 22.13+ (CI exercises Node 22 and 24).

Portable Agent Skill (optional): Assistants supporting Agent Skills can install this repository's GEO workflow guidance using npx skills add AKzar1el/mcp-geo --skill mcp-geo. This installs instructions only, not the MCP server or provider credentials; configure npx -y @digestseo/mcp-geo separately in your MCP host.

Claude Desktop / any MCP client (npx):

{

"mcpServers": { "digestseo": { "command": "npx", "args": ["-y", "@digestseo/mcp-geo"], "env": { "OPENAI_API_KEY": "sk-...", "GEMINI_API_KEY": "your_key_here" } } } }

ChatGPT (remote MCP): ChatGPT does not connect directly to local STDIO MCP servers. For ChatGPT, use the self-hosted remote MCP setup below, or the OpenAI Secure MCP Tunnel setup for a server running on a local/private machine. The public geo-mcp.digestseo.com/mcp endpoint is not a turnkey no-key fresh-scan service.

Perplexity Computer (remote MCP): Perplexity Computer supports custom remote MCP connectors on eligible plans. After self-hosting mcp-geo, open Account settings > Connectors > + Custom connector, choose Remote, name it digestseo, and enter your own deployment's https:// /mcp URL. Use the connector's OAuth option for the Worker flow; configure the required CONNECT_SECRET in your Worker and enter it in the browser gate during connection. Do not use the public geo-mcp.digestseo.com/mcp endpoint as a turnkey no-key scan service. See Perplexity's current Computer connector guidance.

Perplexity Portable Computer (local STDIO): On supported hardware with a Perplexity Pro/Max local model, open Settings > MCP servers > Add server > Local (stdio) and name the server digestseo. Portable requires an absolute Command path: on Windows use C:\Windows\System32\cmd.exe with arguments /d, /s, /c, and npx -y @digestseo/mcp-geo (each on its own line); on Linux use the absolute npx path with -y and @digestseo/mcp-geo as separate arguments. Select Test, then Add. Node.js 22.13+ is required. No provider keys are needed for tool discovery; engine-backed scans can incur provider charges. Portable's local tools are distinct from cloud Computer's Remote/OAuth connector. See the local Portable setup guide and Perplexity's official instructions.

Replit Agent (remote MCP): after self-hosting mcp-geo, open Integrations -> MCP Servers for Replit Agent -> Add MCP server, name it digestseo, and enter your own deployment's https:// /mcp URL. Choose the OAuth flow when prompted: Replit supports OAuth dynamic client registration (DCR), which the self-hosted Worker exposes through its standard discovery and registration endpoints. Select Test & Save, then complete the browser authorization step with the required CONNECT_SECRET. Replit supports remote HTTPS MCP servers rather than this package's local stdio process, so use your configured Worker URL and do not treat the public geo-mcp.digestseo.com/mcp endpoint as a turnkey provider-key service. See Replit's current MCP guide.

Claude Code:

claude mcp add --transport stdio digestseo -s user --env GEMINI_API_KEY=your_key_here -- npx -y @digestseo/mcp-geo

Or install the same local MCP integration through this repository's owner-controlled Claude Code marketplace:

/plugin marketplace add AKzar1el/mcp-geo

/plugin install digestseo-geo@digestseo-mcp

The marketplace plugin uses the repository's .mcp.json to launch npx -y @digestseo/mcp-geo. Zero provider keys are enough for tool discovery; for engine-backed scans, make only the provider keys you want available to the Claude Code process. The direct claude mcp add command above remains the simplest option when you want to attach provider keys explicitly to the server configuration.

Codex CLI:

codex mcp add digestseo -- npx -y @digestseo/mcp-geo

The zero-key command is enough for tool discovery. Add only the provider keys you want with repeated --env NAME=VALUE options before the -- when engine-backed scans are needed.

Amp CLI:

amp mcp add digestseo -- npx -y @digestseo/mcp-geo

Amp runs this as a local STDIO MCP server. The zero-key command is enough for tool discovery; before engine-backed scans, make only the provider keys you want available to the Amp process or configure them in Amp's local MCP env settings instead of committing secrets. See Amp's current MCP guide.

OpenCode v2:

opencode mcp add digestseo --global -- npx -y @digestseo/mcp-geo

OpenCode v2 runs this as a local STDIO server. Omit --global for project-only configuration. Zero keys are enough for MCP tool discovery. For engine-backed scans, edit the generated OpenCode v2 config and add only the provider variables you want under mcp.servers.digestseo.environment, mapping each to an environment reference such as "OPENAI_API_KEY": "{env:OPENAI_API_KEY}"; keep the actual secret value in the process environment rather than in the config file. Verify the connection with opencode mcp list. See the current OpenCode v2 MCP guide.

Mistral Vibe Code: add mcp-geo to the user-level ~/.vibe/config.toml or project-level ./.vibe/config.toml:

[[mcp_servers]]

name = "digestseo" transport = "stdio" command = "npx" args = ["-y", "@digestseo/mcp-geo"]

The zero-key entry is enough for tool discovery. For engine-backed scans, pass only the provider keys you want through Vibe's STDIO environment configuration or the environment inherited by Vibe instead of c