MCP server

DisruptAPI runs a remote Model Context Protocol (MCP) server at /mcp. It gives AI assistants and agents 14 tools that call the same code as the REST API, with the same data, errors and plan limits. Connect it with your normal API key.

What does it speak?#

  • Transport: MCP Streamable HTTP, stateless. Every message is a POST to https://app.disruptapi.com/mcp and gets a plain JSON response. There is no server-sent event stream and no session id, so GET and DELETE return 405, which the specification allows.
  • Protocol versions: 2025-06-18, 2025-03-26 and 2024-11-05. If the client asks for another version, the server answers with 2025-06-18.
  • Capabilities: tools only. resources/list, resources/templates/list and prompts/list return empty lists. The server sends no notifications.
  • Auth: your API key as Authorization: Bearer dk_live_... or X-API-Key. There is no OAuth flow.
  • Batches: JSON-RPC batches of up to 20 messages.

Connect a client#

Keep the key in an environment variable (DISRUPT_KEY below) rather than in a config file you might commit or share.

Setup
claude mcp add --transport http disrupt https://app.disruptapi.com/mcp \
  --header "Authorization: Bearer $DISRUPT_KEY"

Other clients work if they support Streamable HTTP with a custom Authorization header. For clients that only launch local (stdio) servers, use the mcp-remote bridge as in the Claude Desktop example. To check the server by hand:

Raw JSON-RPCcURL
# initialize
curl https://app.disruptapi.com/mcp \
  -H "Authorization: Bearer $DISRUPT_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc": "2.0", "id": 1, "method": "initialize",
       "params": {"protocolVersion": "2025-06-18", "capabilities": {},
                  "clientInfo": {"name": "curl", "version": "1"}}}'

# call a tool
curl https://app.disruptapi.com/mcp \
  -H "Authorization: Bearer $DISRUPT_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc": "2.0", "id": 2, "method": "tools/call",
       "params": {"name": "check_exposure",
                  "arguments": {"items": [{"id": "hub-SEA", "kind": "place", "airport": "SEA"}]}}}'

Which tools are there?#

Each tool's JSON Schema comes from tools/list; item fields are the same as in exposure checks. Read-only tools are annotated readOnlyHint: true; the three watchlist write tools are not, and remove_watchlist_item is marked destructive.

ToolInputsReturns the same as
check_exposureitems (required, 1 to 500 items), min_severity (default moderate)Same as POST /v1/exposure/check
list_signalstype (array of types), min_severity, country, airport, provider, since, status (active, resolved, all), limit (1 to 100, default 20), offsetGET /v1/signals
get_signalsignal_id (required)GET /v1/signals/{id}, with the impact forecast
get_forecastfailure_layer (required), providerGET /v1/forecast
get_airportiata (required)GET /v1/airports/{iata}
get_carriercode (required, IATA airline code)GET /v1/carriers/{code}
list_providersnoneGET /v1/providers
list_eventsprovider, failure_layer, anchor_only, limit (1 to 100, default 20)GET /v1/events (first page only)
list_watchlistsnoneGET /v1/watchlists
get_watchlistwatchlist_id (required), limit (1 to 1,000, default 100)GET /v1/watchlists/{id}
get_watchlist_exposurewatchlist_id (required), min_severity (default moderate)GET /v1/watchlists/{id}/exposure
create_watchlistname (required), description, items (up to 1,000)POST /v1/watchlists
add_watchlist_itemswatchlist_id, items (both required, 1 to 1,000 items)POST /v1/watchlists/{id}/items
remove_watchlist_itemwatchlist_id, item_id (both required)DELETE /v1/watchlists/{id}/items/{item_id}

The server also sends instructions on initialize, telling the assistant to use check_exposure for "is this affected?" questions, to mention n and low_confidence when it reports a forecast, and that DisruptAPI does not report individual flight status.

What does a tool return?#

A successful call returns the REST response body twice: as compact JSON text in content[0].text, and as an object in structuredContent. Errors that the assistant can act on (bad input, unknown ids, plan limits, rate limits) come back as a normal result with isError: true and the message as text, so the model can read it and try again.

tools/call response
{
  "jsonrpc": "2.0",
  "id": 2,
  "result": {
    "content": [
      {
        "type": "text",
        "text": "{\"data\":[{\"item_id\":\"hub-SEA\",\"trip_id\":\"hub-SEA\",\"kind\":\"place\",\"risk_level\":\"high\",\"match_count\":1,\"matches\":[...]}]}"
      }
    ],
    "isError": false,
    "structuredContent": {
      "data": [
        {
          "item_id": "hub-SEA",
          "trip_id": "hub-SEA",
          "kind": "place",
          "risk_level": "high",
          "match_count": 1,
          "matches": ["..."]
        }
      ]
    }
  }
}

Limits and billing#

  • Each tools/call counts as one request against your per-minute rate limit and monthly quota, and appears in GET /v1/usage as MCP <tool name>.
  • An HTTP request without any tools/call (for example initialize, tools/list or ping) is also counted once against the rate limit and quota, so a client that reconnects often uses a little quota.
  • list_signals and list_events count their rows against the daily record budget, like the REST list endpoints. limit is capped at 100, or your plan's page size if smaller (Sandbox: 50); larger values are lowered, not refused.
  • check_exposure and get_watchlist_exposure need exposure checks in your plan, which every current plan includes.

Protocol errors#

HTTPJSON-RPC codeCause
401-32001Missing, unknown or revoked API key. The response has a WWW-Authenticate: Bearer header.
400-32700The body is not JSON.
400-32600Not a JSON-RPC 2.0 message, an empty batch, or more than 20 messages in a batch.
200-32601Unknown method.
200-32602Unknown tool name in tools/call.
429-32000Rate limit or quota reached on a request with no tools/call in it.
405noneGET or DELETE on /mcp. The server is stateless and has no event stream; the header Allow: POST is set.

Notifications (messages without an id) get 202 Accepted with an empty body.

Last updated 2026-11-18. Questions or a mistake on this page? Contact us.