Crawlie vs Tengence GEO Agent
A side-by-side look at the Crawlie and Tengence GEO Agent MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Crawlie for marketing work over a hosted endpoint; choose Tengence GEO Agent 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 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.
Choose Tengence GEO Agent when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
GEO_MCP_TOKEN, SITES_ROOT.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 55/100 · Good | 36/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | GEO_MCP_TOKENSITES_ROOT |
| Verified owner | Community listing | Community listing |
| GitHub stars | 114 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 6 | Not listed |
| Full listing | View Crawlie | View Tengence GEO Agent |
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
Tengence GEO Agent 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"
}
}
}
Tengence GEO Agent
{
"mcpServers": {
"tengence-geo-agent": {
"command": "npx",
"args": [
"-y",
"@tengence/geo-agent"
],
"env": {
"GEO_MCP_TOKEN": "YOUR_GEO_MCP_TOKEN_HERE",
"SITES_ROOT": "YOUR_SITES_ROOT_HERE"
}
}
}
}
Frequently asked questions
Crawlie is categorized under Marketing and uses a remote HTTP/SSE transport. Tengence GEO Agent belongs to Marketing and uses a local stdio subprocess. Pick Crawlie for marketing work and Tengence GEO Agent 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. Tengence GEO Agent 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 tengence-geo-agent 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. Tengence GEO Agent has 36/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.
