Crawlie vs Google Analytics

A side-by-side look at the Crawlie and Google Analytics MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Crawlie logoCrawlieMarketing · Remote HTTP/SSETechnical SEO + GEO (AI-search) site audits: hosted crawls, prioritized fixes, report diffs.53GoodAuth: not declaredGoogle Analytics logoGoogle AnalyticsMarketingMCP server for Google Analytics 4 — reports, realtime data, and admin33EmergingAuth: not declared

Verdict: choose Crawlie for marketing work over a hosted endpoint; choose Google Analytics for marketing. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Crawlie logoChoose 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.
Explore Crawlie

Google Analytics logoChoose Google Analytics when

  • You need dedicated capabilities in the Marketing domain.
Explore Google Analytics

Feature & specification comparison

Rows where the two servers differ are marked.

SpecCrawlie logoCrawlieGoogle Analytics logoGoogle Analytics
CategoryMarketingMarketing
Quality signal53/100 · Good33/100 · Emerging
Install commandConfirmedNot confirmed yet
TransportRemote HTTP/SSE—
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars1150
Directory activity 2 views 0 installs 0 upvotes 0 views 0 installs 0 upvotes
Tools6Not listed

Tools & capabilities

Crawlie tools 6

  • crawl_siteCrawl + audit a whole site (SEO + GEO), returns scores, issues, per-page data
  • audit_urlAudit a single page
  • audit_urlsAudit an explicit list of pages
  • explain_issueWhy a rule matters + how to fix it
  • list_rulesThe full catalogue of checks
  • list_reportsRead saved crawl history

Google Analytics 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 (Claude Desktop / Cursor)
{
  "mcpServers": {
    "crawlie": {
      "url": "https://crawlie.app/mcp"
    }
  }
}

Google Analytics

No confirmed install command for Google Analytics yet — follow the setup steps linked from its listing page rather than a guessed package name.

Frequently asked questions

Crawlie is categorized under Marketing and uses a remote HTTP/SSE transport. Google Analytics belongs to Marketing and uses an install path we have not confirmed yet. Pick Crawlie for marketing work and Google Analytics 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. Google Analytics has no confirmed install command yet — follow its own setup instructions.

Crawlie has no declared pricing — check the project's own site. Google Analytics 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 google-analytics 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 53/100 (Good) with 2 views, 0 installs and 115 GitHub stars. Google Analytics has 33/100 (Emerging) with 0 views, 0 installs and 0 GitHub stars.