A side-by-side look at the AEO Audit and Maxaeo AI Visibility MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose AEO Audit for marketing work over a hosted endpoint; choose Maxaeo AI Visibility MCP for marketing as a local process. You can also run both side by side in one mcpServers block.
check_llms_txt, audit_ai_crawler_readiness, build_ai_visibility_report.Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 35/100 · Fair | 61/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 1 |
| Directory activity | 0 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | Not listed | 3 |
| Full listing | View AEO Audit | View Maxaeo AI Visibility MCP |
No tool names declared yet. Check the project README from the listing page.
check_llms_txtValidate /llms.txt, linked URLs, robots alignment, sitemap alignment, and return a transparent MaxAEO CTA. No MaxAEO APIs are called.audit_ai_crawler_readinessCheck robots rules, AI crawler access basics, homepage metadata, canonical, noindex, and JSON-LD schema. No MaxAEO APIs are called.build_ai_visibility_reportRun local/public-web AI visibility checks and return dual scores, evidence gaps, an action plan, and a transparent MaxAEO CTA.Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
{
"mcpServers": {
"aeo-audit": {
"url": "https://aeo-mcp-server.amdal-dev.workers.dev/mcp"
}
}
}
{
"mcpServers": {
"maxaeo-maxaeo-ai-visibility-mcp": {
"command": "npx",
"args": [
"-y",
"maxaeo-ai-visibility-mcp"
]
}
}
}