Skip to main content
Glama

aeo-mcp

An MCP server that gives AI agents — Claude, Claude Code, Cursor, anything speaking the Model Context Protocol — tools to inspect a website's visibility to AI answer engines. Crawler permissions, llms.txt, structured data, on-page signals, and a full 29-check AI-readiness audit (powered by answer-audit), each one tool call away. Read-only, no API keys, no telemetry.

Claude Desktop using aeo-mcp to inspect The Verge's AI crawler policy

Real session: Claude Desktop discovers The Verge allows GPTBot (OpenAI licensing deal) while blocking ClaudeBot, PerplexityBot, Google-Extended, and CCBot — one tool call.

Install

Claude Code

claude mcp add aeo -- npx -y aeo-mcp

Claude Desktop (claude_desktop_config.json)

{ "mcpServers": { "aeo": { "command": "npx", "args": ["-y", "aeo-mcp"] } } }

Cursor (.cursor/mcp.json)

{ "mcpServers": { "aeo": { "command": "npx", "args": ["-y", "aeo-mcp"] } } }

Related MCP server: mcp-geo

Tools

Tool

When the agent uses it

Input

Returns

audit_url

"How visible is this site to ChatGPT/Perplexity?" — full AEO health check

{ url }

0-100 score, grade, category breakdown, failed/warned checks with fixes

check_ai_crawlers

"Is GPTBot blocked?" — robots.txt policy per AI bot

{ url }

Per-bot allow/block verdicts with the matching rule, plus sitemaps

inspect_llms_txt

"Does this site have llms.txt? Is it valid?"

{ url }

Title, summary, sections with links, structural issues, raw excerpt

extract_structured_data

"What schema markup does this page have?"

{ url }

JSON-LD types, key fields per node, parse errors

extract_page_signals

"Why do engines misread this page?"

{ url }

Title, meta description, h1, canonical, lang, text ratio, heading outline, client-side-rendering flag

Bots checked by check_ai_crawlers: GPTBot, ClaudeBot, PerplexityBot, Google-Extended, CCBot, Bingbot.

Try these prompts

  • "Audit glowlab.com and summarize the top 3 AEO fixes."

  • "Compare the AI crawler policies of nike.com and adidas.com — who is more open to being cited?"

  • "Check if my site has a valid llms.txt, and if not, draft one from my page signals."

Security

The server fetches model-supplied URLs, so it ships with an SSRF guard: http/https only, DNS resolution checked against private and special ranges (loopback, RFC1918, link-local, unique-local, IPv4-mapped forms), re-validation on every redirect hop, 10 s timeout, 2 MB body cap, max 5 redirects. Violations return a clean tool error, never an exception. All tools are read-only and no LLM calls happen inside the server.

Development

npm install
npm run build   # required before npm test (the protocol test runs dist/)
npm test

Tests include a scripted stdio round-trip (initialize → tools/list → tools/call) against the built server. To inspect interactively:

npx @modelcontextprotocol/inspector node dist/index.js

License

MIT © Arthur Carlson

Available Tools

5 tools
audit_urlA

Run a full AI-readiness (AEO) audit of a website: 29 checks across AI crawler access, structured data, content extractability, and answerability, returning a 0-100 score with prioritized fixes. Use when asked how visible a site is to ChatGPT, Perplexity, Gemini, or Claude, or for an overall AEO/AI-SEO health check.

Inputs: url (required).

check_ai_crawlersA

Check whether AI crawlers like GPTBot, ClaudeBot, PerplexityBot, Google-Extended, CCBot, and Bingbot are allowed to read a website, based on its robots.txt. Use when asked about AI visibility, AEO, crawler permissions, or why a site does not appear in ChatGPT or Perplexity.

Inputs: url (required).

extract_page_signalsA

Extract the on-page signals AI engines parse: title, meta description, h1, canonical, lang, text-to-HTML ratio, heading outline, and whether the page looks client-side rendered (invisible to most AI crawlers). Use to diagnose why engines misread or skip a page.

Inputs: url (required).

extract_structured_dataA

Extract and summarize a page's JSON-LD structured data (schema.org): which types exist (Product, Article, FAQPage, Organization), their key fields, and any parse errors. Use when asked whether a page has the schema markup AI answer engines rely on for citations.

Inputs: url (required).

inspect_llms_txtA

Fetch and validate a website's llms.txt file (the Markdown file that tells AI engines what the site is about and which pages matter). Returns its title, summary, sections, links, and any structural issues. Use when asked whether a site has llms.txt or how to improve it.

Inputs: url (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.2/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct aspect of AI readiness: overall audit, crawler permissions, llms.txt, structured data, and page signals. No overlap in purpose.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with underscores, e.g., audit_url, check_ai_crawlers, inspect_llms_txt, extract_structured_data, extract_page_signals.

    Tool Count5/5

    Five tools is well-scoped for the focused domain of AI-readiness auditing. Each tool covers a key area without being overwhelming or too sparse.

    Completeness4/5

    The set covers core AI-readiness checks (crawlers, llms.txt, structured data, on-page signals) and a comprehensive audit. Minor gaps like content quality or answerability simulation are likely integrated into the audit tool.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server exposing Generative Engine Optimization tools to any AI agent, enabling checking of llms.txt, auditing robots.txt for AI crawlers, and validating JSON-LD schema.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Open-source MCP server that audits websites for AI search readiness, providing deterministic scoring (0-100) and prioritized fix lists for metrics like JSON-LD, llms.txt, heading hierarchy, and AI crawler access.
      1
      MIT