Crawlora MCP

Crawlora MCP is a hosted Model Context Protocol server that gives AI clients and agents 445 structured public‑web‑data tools across 30+ categories — search, maps, e‑commerce, social, finance, travel, app stores, media, and reviews — each returning clean, normalized JSON instead of HTML to parse.

Two ways to use it: connect any MCP client to the hosted endpoint (https://mcp.crawlora.net/mcp), or run the small open‑source local server in this repo (npx / Docker, stdio) — both expose the same tools and authenticate with your Crawlora API key. Start free with 2,000 credits/month (no card) at crawlora.net.

Connection

A missing or invalid API key returns 401.

Connect your client

Crawlora MCP works with any MCP‑capable client. Pick yours below — they all point at the same hosted endpoint (https://mcp.crawlora.net/mcp, Streamable HTTP) and authenticate with your CRAWLORA_API_KEY. Prefer keeping the key in an environment variable over pasting it literally, and never commit it. Ready‑to‑paste files for each client live in examples/.

Claude Code (CLI)

claude mcp add --transport http crawlora https://mcp.crawlora.net/mcp \
  --header "Authorization: Bearer ${CRAWLORA_API_KEY}"

Adds at local scope by default. Use --scope user to make it available in every project, or --scope project to write a shared .mcp.json. Confirm with claude mcp list.

Claude Desktop

Settings → Developer → Edit Config, then add to claude_desktop_config.json:

{
  "mcpServers": {
    "crawlora": {
      "url": "https://mcp.crawlora.net/mcp",
      "transport": "streamable-http",
      "headers": { "Authorization": "Bearer YOUR_CRAWLORA_API_KEY" }
    }
  }
}

Cursor

Project‑local .cursor/mcp.json (or ~/.cursor/mcp.json for all projects):

{
  "mcpServers": {
    "crawlora": {
      "url": "https://mcp.crawlora.net/mcp",
      "headers": { "Authorization": "Bearer ${CRAWLORA_API_KEY}" }
    }
  }
}

Codex CLI

codex mcp add crawlora \
  --url https://mcp.crawlora.net/mcp \
  --bearer-token-env-var CRAWLORA_API_KEY

VS Code (GitHub Copilot)

.vscode/mcp.json (project) or your user mcp.json:

{
  "servers": {
    "crawlora": {
      "type": "http",
      "url": "https://mcp.crawlora.net/mcp",
      "headers": { "Authorization": "Bearer ${env:CRAWLORA_API_KEY}" }
    }
  }
}

Windsurf

~/.codeium/windsurf/mcp_config.json (note the serverUrl key):

{
  "mcpServers": {
    "crawlora": {
      "serverUrl": "https://mcp.crawlora.net/mcp",
      "headers": { "Authorization": "Bearer ${env:CRAWLORA_API_KEY}" }
    }
  }
}

Gemini CLI

~/.gemini/settings.json (note the httpUrl key):

{
  "mcpServers": {
    "crawlora": {
      "httpUrl": "https://mcp.crawlora.net/mcp",
      "headers": { "Authorization": "Bearer YOUR_CRAWLORA_API_KEY" }
    }
  }
}

Cline / Roo Code

Add to cline_mcp_settings.json using the generic remote shape — full walkthrough in llms-install.md:

{
  "mcpServers": {
    "crawlora": {
      "url": "https://mcp.crawlora.net/mcp",
      "transport": "streamable-http",
      "headers": { "Authorization": "Bearer ${CRAWLORA_API_KEY}" }
    }
  }
}

Other clients

Any client that speaks Streamable HTTP can use the generic config in examples/mcp.json. stdio‑only clients (e.g. Zed) should run the local server below and point at its npx command.

Run it locally (open‑source server)

This repo also ships a small stdio MCP server (index.mjs) that exposes the same 445 tools, each wrapping the Crawlora REST API (https://api.crawlora.net/api/v1) with your CRAWLORA_API_KEY. Useful if you'd rather run the server yourself than use the hosted endpoint.

# Node 20+ (no install)
CRAWLORA_API_KEY=your-key npx -y crawlora-mcp

# or from a clone
npm install && CRAWLORA_API_KEY=your-key node index.mjs

# or Docker
docker build -t crawlora-mcp . && docker run -i -e CRAWLORA_API_KEY=your-key crawlora-mcp

Client config (stdio):

{
  "mcpServers": {
    "crawlora": {
      "command": "npx",
      "args": ["-y", "crawlora-mcp"],
      "env": { "CRAWLORA_API_KEY": "your-key" }
    }
  }
}

The tool definitions in tools.json are generated from Crawlora's published API catalog; each carries its real input schema and maps to a single REST endpoint.

What you can call (445 tools / 30+ categories)

Full, always‑current tool list with parameters, response examples, and a live Playground: https://crawlora.net/docs.

Why Crawlora

• Normalized JSON per tool — ship data features, not scraper infrastructure.
• No proxies, browsers, or parsers to maintain.
• Pay on success — credit‑based, billed only on 2xx responses.
• One key, 445 tools — search, commerce, social, finance, and more behind a single MCP endpoint.

A good alternative to stitching together SerpApi, Firecrawl, ScraperAPI, or ScrapingBee.

Links

• Website: https://crawlora.net/mcp
• Docs & Playground: https://crawlora.net/docs · https://crawlora.net/playground
• Pricing: https://crawlora.net/pricing
• Server card: https://crawlora.net/.well-known/mcp/server-card.json
• Official MCP registry manifest: server.json

License

See LICENSE. The Crawlora MCP service itself is a hosted SaaS governed by the Crawlora terms; this repository contains connection docs and manifests.