mcpdirectory.dev
9,129 servers · updated 23 Sept

Geo MCP server

community Active last commit today
{
  "mcpServers": {
    "digestseo": {
      "command": "npx",
      "args": [
        "-y",
        "@digestseo/mcp-geo@latest"
      ],
      "env": {
        "OPENAI_API_KEY": "sk-...",
        "GEMINI_API_KEY": "<gemini_api_key>",
        "CONNECT_SECRET": "<connect_secret>",
        "SEED_SECRET": "<seed_secret>",
        "ANTHROPIC_API_KEY": "sk-ant-...",
        "PERPLEXITY_API_KEY": "<perplexity_api_key>"
      }
    }
  }
}
file .mcp.json (in your project root)install npx -y @digestseo/mcp-geoversion 0.3.2

What it does

This server tracks how often your brand is cited by five AI search engines (ChatGPT, Claude, Perplexity, Gemini, Google AI Overviews) and surfaces the results as tools you can query from Claude or other MCP clients. It's for SEO professionals and marketers who want to measure brand visibility in generative AI systems the way Search Console works for Google.

  • Track a brand's citation frequency across AI search engines and get a visibility score for each.
  • Generate a strategic report analyzing which AI engines mention your brand and where content gaps exist.
  • Compare your brand's visibility against competitors across the five supported engines.

Tools this server exposes

ToolDoes
track_brandCreate a new brand to monitor with auto-generated tracking prompts.
refresh_brandRun a scan of the tracked brand across all five AI engines.
check_visibilityRetrieve current citation scores and visibility data for a tracked brand.
list_brandsList all brands currently being tracked.
generate_promptsGenerate tracking prompts for a brand.
visibility.checkCheck AI visibility metrics for a brand (hosted endpoint).
visibility.compareCompare visibility metrics between brands (hosted endpoint).
visibility.citationsRetrieve citation excerpts from Perplexity and Claude for a brand (hosted endpoint).
visibility.content_gapsIdentify content gaps based on AI engine visibility analysis (hosted endpoint).

Before you enable it

An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.