NotFair GoogleAds vs Crawlie
A side-by-side look at the NotFair GoogleAds 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 NotFair GoogleAds 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.
Which MCP server should you choose?
Choose NotFair GoogleAds when
- You need dedicated capabilities in the Marketing domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: OAuth 2.0.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 49/100 · Fair | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Remote HTTP/SSE |
| Auth | OAuth 2.0 | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 4,040 | 115 |
| Directory activity | 1 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | 6 |
| Full listing | View NotFair GoogleAds | View Crawlie |
Tools & capabilities
NotFair GoogleAds tools
No tool names declared yet. Check the project README from the listing page.
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
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.
NotFair GoogleAds
{
"mcpServers": {
"notfair-googleads": {
"url": "https://notfair.co/api/mcp/notfair"
}
}
}
Crawlie
{
"mcpServers": {
"crawlie": {
"url": "https://crawlie.app/mcp"
}
}
}
Frequently asked questions
NotFair GoogleAds is categorized under Marketing and uses a remote HTTP/SSE transport. Crawlie belongs to Marketing and uses a remote HTTP/SSE transport. Pick NotFair GoogleAds for marketing work and Crawlie 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.
NotFair GoogleAds has no declared pricing — check the project's own site. Auth: oauth 2.0. Crawlie 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 notfair-googleads and crawlie as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, NotFair GoogleAds has a quality signal of 49/100 (Fair) with 1 views, 0 installs and 4,040 GitHub stars. Crawlie has 53/100 (Good) with 2 views, 0 installs and 115 GitHub stars.