DigestSEO AI Visibility MCP Server

Track how ChatGPT, Claude, Perplexity, Gemini, and Google AI Overviews cite your brand. Exposed over MCP by the digestseo ai visibility mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

Runs locally over stdio with your own API keys — all data stays on your machine (see Privacy Policy). Set at least one engine key (OPENAI_API_KEY, ANTHROPIC_API_KEY, GEMINI_API_KEY, PERPLEXITY_API_KEY, SERPAPI_API_KEY); engines without a key skip gracefully.

Its toolset

Everything the assistant can do here goes through one of these:

• OpenAI — ChatGPT engine. ~€0.0004 per prompt with gpt-4o-mini. Batch path roughly halves that. platform.openai.com
• Anthropic — Claude engine, plus prompt generation and content-gap analysis (both call Claude Haiku). ~€0.0002 per prompt. Free trial credits are usually enough
• Perplexity — Perplexity Sonar engine. ~€0.005-0.008 per prompt. Paid only. perplexity.ai/settings/api
• SerpAPI — Google AI Overviews engine. ~€0.005 (free tier) / ~€0.0015 (volume) per prompt. Free tier covers ~100 calls/month — enough for development
• visibility.check — Latest AI visibility snapshot across all configured engines for a tracked brand, with per-engine scores, winning prompts, and losing prompts
• visibility.history — Time-series history of overall and per-engine visibility, bucketed daily or weekly
• visibility.compare — Share-of-voice comparison against competitor domains, with prompts you win and prompts they win
• visibility.citations — The actual citation events — prompt, engine, response excerpt, citation type, brand URL when present
• visibility.content_gaps — Prioritized Claude-Haiku-generated content recommendations targeting your losing prompts
• visibility.refresh — Manually trigger a fresh scan across every engine whose API key is set
• track_brand — Start tracking a brand: creates it locally and generates its buyer-intent prompt set (Claude Haiku when ANTHROPIC_API_KEY is set, three starter
• list_brands — List tracked brands with domains, competitors, and active prompt counts

Configuration

You will need 8 environment variables: OPENAI_API_KEY, GEMINI_API_KEY, ANTHROPIC_API_KEY, PERPLEXITY_API_KEY, SERPAPI_API_KEY, CONNECT_SECRET, SEED_SECRET, TURNSTILE_SITE_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

When to reach for it

Among the AI and media services options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. DigestSEO AI Visibility's toolset — OpenAI, Anthropic, Perplexity and 11 more — is a fair guide to whether it matches your workflow. It is maintained by AKzar1el; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against DigestSEO AI Visibility's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch DigestSEO AI Visibility.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the digestseo ai visibility mcp server does with a few real requests.