The hosted MCP server

Connect Claude, Claude Code, Cursor, or Codex to crawlie.app/mcp and let your agent run crawls and read reports.

What it is

Crawlie Cloud speaks the Model Context Protocol at:

https://crawlie.app/mcp

Point an MCP client at that URL and your agent can start crawls, poll them, and work with your reports — the same data you see in the dashboard, in your workspace, on your plan.

Connect your client

Pick your client for the exact setup:

  1. In Claude (web or desktop), open Settings → Connectors → Add custom connector.
  2. Paste the server URL:
    https://crawlie.app/mcp
  3. Claude opens a Crawlie sign-in — approve it and you're connected. No keys to paste.

Try: "Crawl example.com and walk me through the top fixes."

Custom connectors require a paid Claude plan.

Using something else? Any MCP client works: give it https://crawlie.app/mcp — clients that speak OAuth open a Crawlie sign-in, and everything else can send an API key as a bearer token.

The tools

ToolWhat the agent gets
crawl_siteStart a crawl of a site (streams progress, or returns a job to poll).
audit_urlAudit a single URL.
crawl_statusCheck on a running crawl.
list_reportsBrowse the workspace’s reports.
get_reportPull a full report.
top_fixesThe highest-impact fixes from a report, ranked.
geo_gapsWhere the site falls short for AI search.
affected_urlsEvery URL a given issue affects.
diff_reportsCompare two crawls.

Good to know

  • Crawls started by an agent spend crawl credits like any other crawl, and respect your plan’s page caps.
  • The prompt patterns that work well (“audit this site and fix the top issues”) are collected in the prompt library.
  • Running fully local instead? The open-source crawler ships its own MCP server — same idea, your machine.

Still stuck? Email us — a human replies, usually within a day.