Crawlie vs Seovendor
A side-by-side look at the Crawlie and Seovendor MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
S
SeovendorMarketing · Remote HTTP/SSEA FastMCP server that exposes SV's SEO and GEO tools natively to AI agents — Claude Desktop, Claude Code, Cursor, and any MCP-capable host. Built directly on the sv-cli core library: no duplicated resolver, auth, or async-task logic.44FairAuth: not declaredVerdict: choose Crawlie for marketing work over a hosted endpoint; choose Seovendor for marketing over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Crawlie when
- You need dedicated capabilities in the Marketing domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
crawl_site, audit_url, audit_urls.
SChoose Seovendor when
- You need dedicated capabilities in the Marketing domain.
- You prefer a remote HTTP/SSE transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | S Seovendor | |
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 55/100 · Good | 44/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | 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 | 6 | Not listed |
| Full listing | View Crawlie | View Seovendor |
Tools & capabilities
Crawlie tools 6
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 history
Seovendor 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.
Crawlie
{
"mcpServers": {
"crawlie": {
"url": "https://crawlie.app/mcp"
}
}
}
Seovendor
{
"mcpServers": {
"seovendor": {
"url": "https://seovendor.co/api/mcp"
}
}
}
Frequently asked questions
Crawlie is categorized under Marketing and uses a remote HTTP/SSE transport. Seovendor belongs to Marketing and uses a remote HTTP/SSE transport. Pick Crawlie for marketing work and Seovendor 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.
Crawlie has no declared pricing — check the project's own site. Seovendor 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 crawlie and seovendor as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Crawlie has a quality signal of 55/100 (Good) with 1 views, 0 installs and 114 GitHub stars. Seovendor has 44/100 (Fair) with 2 views, 0 installs and 0 GitHub stars.