Aeo Scanner MCP Server

If you already use Aeo Scanner MCP, the aeo scanner mcp mcp server is the piece that lets your assistant work with it directly. AI search visibility audit for any website. Three scores, one scan.

What the server does

• AEO Score (0-100): — How well AI search engines (ChatGPT, Perplexity, Google AI Overviews) can find, read, and cite your content
• GEO Score (0-100): — How likely AI is to cite your site as a source — citation readiness for AI-generated answers
• Agent Readiness (0-100): — How easily AI agents can understand, interact with, and transact on your site
• Mention Readiness (0-100): — Predicts how likely AI will mention your brand, based on 12 research-backed signals
• AI Identity Card: — How AI currently perceives your brand — gaps, citable claims, detected competitors
• Business Profile: — Auto-detected business type (commerce/saas/media/general) with which scores matter most

Installation

aeo-scanner on PyPI is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• scan_site — Quick triple-score scan + AI Identity Card + mention readiness + business profile + top issues
• audit_site — Full 58+ check breakdown across 12 categories (4 AEO + 4 GEO + 4 Agent)
• compare_sites — Two-site gap analysis + category winners + overtake fix code
• fix_site — Generated fix code with two-tier score projections — apply directly with Claude Code

Credentials and setup notes

Configuration is passed through the environment: AEO_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Aeo Scanner MCP's toolset — scan_site, audit_site, compare_sites and 1 more — is a fair guide to whether it matches your workflow. It is maintained by convrgent; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.