ReefAPI MCP

One MCP server for 150+ live web-data APIs — search engines, social media, e-commerce, real estate, jobs, travel, news, finance, and company/domain/people intelligence. The assistant discovers the right engine, then pulls clean JSON from sites that block scrapers (captcha, login, JS, anti-bot).

• 🌐 Homepage: https://reefapi.com
• 📚 Docs: https://reefapi.com/docs
• 🔌 MCP guide: https://reefapi.com/mcp
• 🟢 Status: https://reefapi.com/status

Why one server, not one tool per API

Emitting one tool per API blows past the ~30–50-tool ceiling where agents stop picking the right tool. ReefAPI uses dynamic discovery instead: five generic tools let the assistant find the right engine, then call it. Discovery is keyless; only `call_engine` needs a key. Failed or blocked calls cost nothing.

Tools

The intended path is `search_engines` (or `get_catalog`) → `get_engine_schema` → `get_action_schema` → `call_engine`.

Connect (remote — recommended)

Add to Claude Desktop, Cursor, Windsurf, or any client that takes a remote MCP URL:

{
  "mcpServers": {
    "reefapi": {
      "url": "https://api.reefapi.com/mcp",
      "headers": { "Authorization": "Bearer YOUR_REEFAPI_KEY" }
    }
  }
}

Claude Code (CLI):

claude mcp add --transport http reefapi https://api.reefapi.com/mcp \
  --header "Authorization: Bearer YOUR_REEFAPI_KEY"

Get a free key (1,000 credits, no card) at https://reefapi.com.

Run it locally (stdio)

pip install -r requirements.txt
export REEFAPI_KEY=ak_live_your_key   # Windows: set REEFAPI_KEY=...
python server.py                      # stdio transport

Then point your client at `python /path/to/server.py`. The same file also serves the streamable-HTTP

transport with `MCP_TRANSPORT=streamable-http` (used by the hosted endpoint above).

What you can ask

Each example below is answered by one engine; the link goes to that engine's parameters and response shape.

• *"What are people saying about the new iPhone on Reddit?"* → `reddit`
• *"Get current Zillow listings in Austin under $500k."* → `zillow`
• *"Is the domain `coolstartup.ai` available?"* → `domain-availability`
• *"Compare Amazon prices for AirPods Pro."* → `amazon`
• *"Top Hacker News stories right now."* → `hackernews`
• *"What tech stack does stripe.com run on?"* → `domain-intel`
• *"Find remote backend jobs posted this week."* → `global-jobs`

You never have to name the engine yourself — that is what `search_engines` is for. The links are there for

when you want to see the exact params and fields before wiring a call.

Coverage

150+ engines across Search/SEO, Social Media, E-commerce, Real Estate, Jobs, Travel, News, Finance,

Media/Film, Reputation/Reviews, Company/Domain/People intelligence, and developer utilities.

Browse the full catalog at reefapi.com/docs, or call `get_catalog()` for the

live list. A few of the most-used ones:

Every engine returns the same `{ ok, data, meta, error }` envelope and draws on one shared credit pool.

License

MIT — see LICENSE. The APIs are a hosted service with a free tier; see https://reefapi.com.