AEO Audit vs AI Readiness
A side-by-side look at the AEO Audit and AI Readiness 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 AI Readiness for marketing as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose AEO Audit when
- You need dedicated capabilities in the Marketing domain.
- You prefer a remote HTTP/SSE transport.
Choose AI Readiness when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 35/100 · Fair | 51/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 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View AEO Audit | View AI Readiness |
Tools & capabilities
AEO Audit tools
No tool names declared yet. Check the project README from the listing page.
AI Readiness tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
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.
AEO Audit
{
"mcpServers": {
"aeo-audit": {
"url": "https://aeo-mcp-server.amdal-dev.workers.dev/mcp"
}
}
}
AI Readiness
{
"mcpServers": {
"epistemedeus-ai-readiness": {
"command": "npx",
"args": [
"-y",
"github:epistemedeus/ai-readiness"
]
}
}
}
Frequently asked questions
AEO Audit is categorized under Marketing and uses a remote HTTP/SSE transport. AI Readiness belongs to Marketing and uses a local stdio subprocess. Pick AEO Audit for marketing work and AI Readiness for marketing.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
AEO Audit has no declared pricing — check the project's own site. AI Readiness is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add aeo-audit and epistemedeus-ai-readiness as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, AEO Audit has a quality signal of 35/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. AI Readiness has 51/100 (Good) with 5 views, 0 installs and 0 GitHub stars.