A side-by-side look at the Bottally and Crawlie MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Bottally for marketing work over a hosted endpoint; choose Crawlie for marketing over a hosted endpoint. You can also run both side by side in one mcpServers block.
crawl_site, audit_url, audit_urls.Rows where the two servers differ are marked.
| Spec | B Bottally | |
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 43/100 · Fair | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Freemium | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 114 |
| Directory activity | 1 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | 6 |
| Full listing | View Bottally | View Crawlie |
No tool names declared yet. Check the project README from the listing page.
crawl_siteCrawl + audit a whole site (SEO + GEO), returns scores, issues, per-page dataaudit_urlAudit a single pageaudit_urlsAudit an explicit list of pagesexplain_issueWhy a rule matters + how to fix itlist_rulesThe full catalogue of checkslist_reportsRead saved crawl historyPaste 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": {
"bottally": {
"command": "npx",
"args": [
"-y",
"bottally"
]
}
}
}
{
"mcpServers": {
"crawlie": {
"url": "https://crawlie.app/mcp"
}
}
}