AEO tools for AI agents: crawler permissions, llms.txt, structured data, AI-readiness audit.
Aeo MCP server exists for a simple reason — assistants are far more useful when they can act on Aeo directly instead of describing what you should do. AEO tools for AI agents: crawler permissions, llms.txt, structured data, AI-readiness audit.
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.
Installation goes through your MCP client rather than a global install: point it at aeo-mcp on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Once Aeo is connected, these are the calls the assistant has available:
audit_url — "How visible is this site to ChatGPT/Perplexity?" — full AEO health checkcheck_ai_crawlers — "Is GPTBot blocked?" — robots.txt policy per AI botinspect_llms_txt — "Does this site have llms.txt? Is it valid?"extract_structured_data — "What schema markup does this page have?"extract_page_signals — "Why do engines misread this page?"Among the search and retrieval 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. Aeo's toolset — audit_url, check_ai_crawlers, inspect_llms_txt and 2 more — is a fair guide to whether it matches your workflow. It is maintained by arthurcarlsonn; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| audit_url | "How visible is this site to ChatGPT/Perplexity?" — full AEO health check |
| check_ai_crawlers | "Is GPTBot blocked?" — robots.txt policy per AI bot |
| inspect_llms_txt | "Does this site have llms.txt? Is it valid?" |
| extract_structured_data | "What schema markup does this page have?" |
| extract_page_signals | "Why do engines misread this page?" |
**Cursor** (`.cursor/mcp.json`)
```json
{ "mcpServers": { "aeo": { "command": "npx", "args": ["-y", "aeo-mcp"] } } }Configuration as documented by the project. Restart the client after saving.
The simplest web tool that matters — fetch any URL and get model-ready markdown back.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Search built for AI, not humans — semantic web search that returns model-ready content, plus code context.
Answers, not links — delegate questions to Perplexity's search-grounded models and get cited responses back.
Put 6,000+ pre-built scrapers at your assistant's fingertips through one MCP endpoint.