Crawlora MCP
Official# Crawlora MCP
[](https://crawlora.net/mcp?utm_source=github&utm_medium=referral&utm_campaign=crawlora-mcp)
[](https://crawlora.net/docs?utm_source=github&utm_medium=referral&utm_campaign=crawlora-mcp)
[](https://modelcontextprotocol.io)
[](https://smithery.ai/servers/crawlora/crawlora)
[](https://glama.ai/mcp/servers/Crawlora-org/crawlora-mcp)
**Crawlora MCP** is a **hosted** Model Context Protocol server that gives AI clients and
agents **1414 structured public‑web‑data tools** across 154 platform groups — 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](https://crawlora.net?utm_source=github&utm_medium=referral&utm_campaign=crawlora-mcp)**.
## Connection
| | |
|---|---|
| **Endpoint** | `https://mcp.crawlora.net/mcp` |
| **Transport** | Streamable HTTP |
| **Auth** | `Authorization: Bearer <CRAWLORA_API_KEY>` (preferred) — `x-api-key: <key>` also accepted |
| **Get a key** | [https://crawlora.net](https://crawlora.net?utm_source=github&utm_medium=referral&utm_campaign=crawlora-mcp) (free 2,000 credits/mo) |
| **Server card** | https://crawlora.net/.well-known/mcp/server-card.json |
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/`](examples/).
### Claude Code (CLI)
```bash
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`:
```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):
```json
{
"mcpServers": {
"crawlora": {
"url": "https://mcp.crawlora.net/mcp",
"headers": { "Authorization": "Bearer ${CRAWLORA_API_KEY}" }
}
}
}
```
### Codex CLI
```bash
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`:
```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):
```json
{
"mcpServers": {
"crawlora": {
"serverUrl": "https://mcp.crawlora.net/mcp",
"headers": { "Authorization": "Bearer ${env:CRAWLORA_API_KEY}" }
}
}
}
```
### Gemini CLI
`~/.gemini/settings.json` (note the `httpUrl` key):
```json
{
"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`](llms-install.md):
```json
{
"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`](examples/mcp.json). **stdio‑only** clients (e.g. Zed) should run the
[local server](#run-it-locally-open-source-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 **1414
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.
```bash
# 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):
```json
{
"mcpServers": {
"crawlora": {
"command": "npx",
"args": ["-y", "crawlora-mcp"],
"env": { "CRAWLORA_API_KEY": "your-key" }
}
}
}
```
The tool definitions in [`tools.json`](tools.json) are generated from Crawlora's published API
catalog; each carries its real input schema and maps to a single REST endpoint.
## Hosted MCP (recommended)
Just paste the URL into your client settings. No Node.js required.
```text
https://mcp.crawlora.net/mcp
```
Header:
`x-api-key`: `<your-api-key>`
Get a key at [crawlora.net](https://crawlora.net?utm_source=github&utm_medium=referral&utm_campaign=crawlora-mcp).
Every account includes **2,000 free credits / month** with no credit card required.
---
## What you can call (1414 tools / 12 categories)
See [`tools.json`](./tools.json) or your MCP client UI for exact schemas. Below is a overview by category:
| Category | Highlights |
|---|---|
| **Search & Web** | `google_search`, `google_news`, `bing_search`, `duckduckgo_search`, `baidu_search`, `brave_search`, `startpage_search`, `yandex_search`, `kagi_search`, `web_scrape`, `web_parse` |
| **Maps & Places** | `google_maps_search`, `google_maps_place`, `google_maps_reviews`, `google_maps_photos` |
| **Marketplace & Products** | `amazon_search`, `amazon_product`, `amazon_reviews`, `walmart_search`, `ebay_search`, `etsy_search`, `shopify_store`, `target_search`, `doordash_store`, `doordash_feed`, `ubereats_store` |
| **Social & Profiles** | `twitter_user`, `twitter_tweet`, `instagram_user`, `reddit_post`, `reddit_comments`, `threads_user`, `tiktok_user` |
| **Finance & Markets** | `google_finance_search`, `google_finance_quote`, `yahoo_finance_quote`, `polymarket_events`, `kalshi_markets` |
| **Travel & Lodging** | `airbnb_search`, `airbnb_room`, `tripadvisor_search`, `booking_search` |
| **Jobs & Companies** | `linkedin_jobs`, `indeed_jobs`, `glassdoor_company`, `pitchbook_company` |
| **Media & Audio** | `youtube_video`, `youtube_transcript`, `spotify_artist`, `apple_podcasts_show` |
| **App Stores** | `appstore_app`, `googleplay_app` |
| **Reviews & Q&A** | `trustpilot_reviews`, `g2_reviews`, `capterra_product`, `goodreads_book` |
---
## Why Crawlora MCP?
- **One key, 1414 tools** — search, commerce, social, gaming, 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](https://crawlora.net/mcp?utm_source=github&utm_medium=referral&utm_campaign=crawlora-mcp)
- Docs & Playground: [https://crawlora.net/docs](https://crawlora.net/docs?utm_source=github&utm_medium=referral&utm_campaign=crawlora-mcp) · [https://crawlora.net/playground](https://crawlora.net/playground?utm_source=github&utm_medium=referral&utm_campaign=crawlora-mcp)
- Pricing: [https://crawlora.net/pricing](https://crawlora.net/pricing?utm_source=github&utm_medium=referral&utm_campaign=crawlora-mcp)
- Server card: https://crawlora.net/.well-known/mcp/server-card.json
- Official MCP registry manifest: [`server.json`](server.json)
## License
See [`LICENSE`](LICENSE). The Crawlora MCP service itself is a hosted SaaS governed by the
[Crawlora terms](https://crawlora.net?utm_source=github&utm_medium=referral&utm_campaign=crawlora-mcp); this repository contains connection docs and manifests.
TDQS
Scored across 3122 tools
Although each tool has a site-specific purpose, the set contains hundreds of near-identical families (e.g. brand-pinned Shopify product/collection/page tools, every news site's article/author/headlines/news/sections quartet), so an agent faces severe misselection risk. At 3,122 tools, overlapping resource-action boundaries are inevitable despite detailed descriptions.
Most tools follow a site-or-brand prefix plus snake_case action (e.g. apple_books_search, github_repo, nyt_headlines), which is readable. However, several generic tools lack any prefix (extract, web_scrape, brand_retrieve, usage_endpoints), and some families mix conventions (google_finance_* vs google_map_* vs google_maps-like references), keeping this from being fully predictable.
3,122 tools is an extreme count for any single MCP server and vastly exceeds the practical limit for coherent agent selection. Even if individually useful, the surface is far too large to be well-scoped as one tool set.
The server covers an unusually broad range of public web sources with search/browse/detail patterns, so many verticals have substantial read-only coverage. Still, as a universal scraper it has obvious gaps across sites and domains, and it offers essentially no write/lifecycle operations beyond monitors, leaving notable workarounds for agents.