Google Analytics vs Crawlie

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

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

Verdict: choose Google Analytics for marketing work; 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?

Google Analytics logoChoose Google Analytics when

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

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

Feature & specification comparison

Rows where the two servers differ are marked.

SpecGoogle Analytics logoGoogle AnalyticsCrawlie logoCrawlie
CategoryMarketingMarketing
Quality signal33/100 · Emerging53/100 · Good
Install commandNot confirmed yetConfirmed
Transport—Remote HTTP/SSE
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars0115
Directory activity 0 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
ToolsNot listed6

Tools & capabilities

Google Analytics 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 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

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.

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.

Crawlie

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "crawlie": {
      "url": "https://crawlie.app/mcp"
    }
  }
}

Frequently asked questions

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

Google Analytics has no declared pricing — check the project's own site. 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 google-analytics and crawlie as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Google Analytics has a quality signal of 33/100 (Emerging) with 0 views, 0 installs and 0 GitHub stars. Crawlie has 53/100 (Good) with 2 views, 0 installs and 115 GitHub stars.