Shipwork SEO Checks vs Crawlie

In-depth architectural comparison of the Shipwork SEO Checks and Crawlie MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

Which MCP Server Should You Choose?

S

Choose Shipwork SEO Checks when:

• You need dedicated capabilities in the Marketing domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: API Key required (Freemium).

Explore Shipwork SEO Checks Details

Choose Crawlie when:

• You need dedicated capabilities in the Marketing domain.
• You prefer remote streaming HTTP/SSE transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: crawl_site, audit_url, audit_urls.

Explore Crawlie Details

Feature & Specification Comparison

Specification	S Shipwork SEO Checks Marketing	Crawlie Marketing
Summary	Hosted MCP tools for technical SEO audits, URL status and indexability, sitemaps, and site scores. Sign in at shipwork.io/account to create a personal MCP URL; tool calls use that account allowance.	Technical SEO + GEO (AI-search) site audits: hosted crawls, prioritized fixes, report diffs.
Category & Scope	Marketing	Marketing

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "shipwork-seo-checks": {
      "command": "npx",
      "args": [
        "-y",
        "shipwork-seo-checks"
      ]
    }
  }
}

{
  "mcpServers": {
    "crawlie": {
      "url": "https://crawlie.app/mcp"
    }
  }
}

Related MCP Server Comparisons