Aeonos vs SEOcrawl AI
A side-by-side look at the Aeonos and SEOcrawl AI MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
S
SEOcrawl AISecurity · Remote HTTP/SSELive Google Search Console data, keyword/page analysis, site audit and SEO tasks from SEOcrawl AI.42FairAuth: not declaredVerdict: choose Aeonos for security work as a local process; choose SEOcrawl AI for security over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Aeonos when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
AEONOS_PRIVATE_KEY. - You want tools like
aeonos_query, aeonos_audit, aeonos_schema.
SChoose SEOcrawl AI when
- You need dedicated capabilities in the Security domain.
- You prefer a remote HTTP/SSE transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | S SEOcrawl AI | |
|---|---|---|
| Category | Security | Security |
| Quality signal | 53/100 · Good | 42/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | AEONOS_PRIVATE_KEY | None listed |
| Verified owner | Community listing |
Tools & capabilities
Aeonos tools 5
aeonos_queryAEO/GEO questions, citation tactics, quick winsaeonos_auditFull audit — AI readiness score, P1/P2/P3 roadmapaeonos_schemaProduction-ready JSON-LD Schema.org markupaeonos_llms_txtComplete llms.txt for AI crawler ingestionaeonos_progressAEO Four Layers scorecard (SXO/AIO/GEO/AEO)
SEOcrawl AI 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.
Aeonos
{
"mcpServers": {
"aeonos": {
"command": "npx",
"args": [
"-y",
"aeonos-mcp"
],
"env": {
"AEONOS_PRIVATE_KEY": "YOUR_AEONOS_PRIVATE_KEY_HERE"
}
}
}
}
SEOcrawl AI
{
"mcpServers": {
"seocrawl-ai": {
"url": "https://seocrawl.ai/mcp"
}
}
}
Frequently asked questions
Aeonos is categorized under Security and uses a local stdio subprocess. SEOcrawl AI belongs to Security and uses a remote HTTP/SSE transport. Pick Aeonos for security work and SEOcrawl AI for security.
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.
Aeonos has no declared pricing — check the project's own site. SEOcrawl AI has no declared pricing — check the project's own site. 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 aeonos and seocrawl-ai as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Aeonos has a quality signal of 53/100 (Good) with 1 views, 0 installs and 0 GitHub stars. SEOcrawl AI has 42/100 (Fair) with 2 views, 0 installs and 0 GitHub stars.