One web scraping MCP server
for 165 live data APIs

Five tools: discover, then call

The server exposes exactly five tools. Four are keyless discovery tools an agent uses to find the right engine and build a correct request; the fifth runs it. This discovery-first flow is why an agent can work across 165 APIs without any of them hard-coded into its prompt.

Flow: search_engines → get_engine_schema → get_action_schema → call_engine. The agent never has to know the engine roster in advance — it discovers what it needs at call time.

Add the server to your client

The remote MCP endpoint is https://api.reefapi.com/mcp (streamable-HTTP). Point any MCP client at it and authorize with your ReefAPI key.

// claude_desktop_config.json  (Claude Desktop)
// ~/.cursor/mcp.json          (Cursor — same shape)
{
  "mcpServers": {
    "reefapi": {
      "url": "https://api.reefapi.com/mcp",
      "headers": { "Authorization": "Bearer ak_live_your_key" }
    }
  }
}

# Claude Code (CLI) — add the remote server once
claude mcp add --transport http reefapi https://api.reefapi.com/mcp \
  --header "Authorization: Bearer ak_live_your_key"

Discovery tools work without a key; calls authenticate with your ReefAPI key. Get one free at reefapi.com/signup — 1,000 credits, no card.

What a prompt turns into

Each natural-language ask resolves to one call_engine tool call and comes back as a clean JSON envelope the agent can reason over directly.

call_engine("amazon", "offers", {
  "asin": "B0C1234567", "domain": "com"
})

{
  "ok": true,
  "data": {
    "asin": "B0C1234567",
    "buybox": { "price": 29.99, "currency": "USD", "seller": "Amazon.com" },
    "offers": [
      { "price": 27.40, "condition": "new", "seller": "TechDeals", "prime": true }
    ]
  },
  "meta": { "engine": "amazon", "credits": 1 },
  "error": null
}

call_engine("reddit", "search_comments", {
  "query": "Anker 737 power bank", "sort": "new", "limit": 25
})

{
  "ok": true,
  "data": {
    "query": "Anker 737 power bank",
    "comments": [
      { "id": "kd9f2a1", "author": "gadget_nomad", "subreddit": "batteries",
        "body": "The 737 holds a charge for weeks — worth it.",
        "score": 42, "created_utc": 1752600000 }
    ]
  },
  "meta": { "engine": "reddit", "credits": 1 },
  "error": null
}

call_engine("zillow", "search", {
  "location": "Austin, TX", "max_price": 600000, "beds_min": 3
})

{
  "ok": true,
  "data": {
    "location": "Austin, TX", "count": 128,
    "listings": [
      { "zpid": "70982315", "address": "1204 Maple St, Austin, TX 78702",
        "price": 549000, "beds": 3, "baths": 2, "sqft": 1680,
        "status": "for_sale" }
    ]
  },
  "meta": { "engine": "zillow", "credits": 1 },
  "error": null
}

One key, one pool, no charge for misses

{
  "ok": false,
  "data": null,
  "meta": { "engine": "amazon", "credits": 0 },
  "error": { "code": "UPSTREAM_BLOCKED", "message": "Target returned a challenge; try again." }
}

See the full credit table and free tier on pricing.

The same engines over plain HTTP

MCP is a convenience layer over the REST gateway, not a separate product. Every engine is reachable at POST https://api.reefapi.com/<engine>/v1/<action> with an x-api-key header — same params, same credit pool, same envelope.

# Same engines, same envelope — over plain HTTP (no MCP client)
curl -X POST https://api.reefapi.com/amazon/v1/offers \
  -H "x-api-key: ak_live_your_key" \
  -H "content-type: application/json" \
  -d '{ "asin": "B0C1234567", "domain": "com" }'

MCP server questions