The schema tools mean an agent never needs the engine roster in its prompt — it searches, reads the exact parameter contract, then makes one call. Because discovery is keyless and unmetered and failed calls return zero credits, the exploration that usually costs money costs nothing here.
A remote server with five tools. Four are keyless discovery tools that find an engine and its exact input contract; the fifth runs the call and returns the result in one clean JSON envelope.
- search_engines, which finds the right engine from a plain-language need, and get_catalog, which lists every engine and category on the account
- get_engine_schema and get_action_schema, giving the actions, required and optional parameters, types and enums before a call is built
- call_engine, which runs the request and returns live data in a consistent envelope
- Rotation, residential IPs and anti-bot handling on the server side — no proxy pool to run and no per-site scraper to write
- Discovery unmetered, and calls that fail, time out or are blocked charged zero credits
A ReefAPI key sent as a bearer token to the remote streamable HTTP endpoint. The four discovery tools work without it; only call_engine authenticates and spends, and every engine draws from the same account balance.
One command plus a key — claude mcp add --transport http reefapi https://api.reefapi.com/mcp \ --header "Authorization: Bearer YOUR_REEFAPI_KEY", then supply credentials