MCP server

Set up a client#

For an MCP client that supports remote Streamable HTTP servers with custom headers, the configuration is the URL https://api.ordermap.si/mcp and the header Authorization: Bearer <your key>. The X-API-Key header works too. Clients differ in the file they read and in what they call the keys, so use their documentation for the exact shape. A common one:

{
  "mcpServers": {
    "ordermap": {
      "url": "https://api.ordermap.si/mcp",
      "headers": { "Authorization": "Bearer <your key>" }
    }
  }
}

claude mcp add --transport http ordermap https://api.ordermap.si/mcp \
  --header "Authorization: Bearer $ORDERMAP_API_KEY"

• Clients must accept both application/json and text/event-stream.
• The Developers tab of the terminal shows the tool list and a ready-made configuration.
• Create a key first: see Authentication.

How the tools behave#

• There are 48 read-only tools, one per major endpoint, named after it: /v1/options/flow/stats is options_flow_stats. tools/list returns the exact input schemas.
• A tool's arguments are the endpoint's query parameters, with lists as JSON arrays and numbers and booleans as such. A paginated tool takes cursor_id and returns pagination.next_cursor_id like the REST endpoint.
• A successful call returns the endpoint's envelope as the tool's structured content (and as text).
• A failed call is a tool error (isError: true) whose content is the API error object, so the assistant sees code, message and retry_after_ms.
• Tools never place orders and expose no account or billing data.
• The screener (ninety-plus filters) and the ticker search are REST-only. Reference-data and bulk endpoints are REST-only by design, to keep the tool list small.

Limits#

• Every HTTP request to `/mcp` is one request against your rate limit, including initialize, tools/list and every tools/call. See Rate limits.
• JSON-RPC batches are rejected (400). Send one message per request.
• A message may be at most 256 KiB and a tool result at most 2 MiB. A larger result is a range_too_large tool error: narrow the query or lower limit.
• The MCP endpoint reports protocol-level failures as JSON-RPC errors and endpoint failures as tool errors.

Call a tool directly#

Any HTTP client can speak the protocol. This calls options_flow_stats:

curl -sS "https://api.ordermap.si/mcp" \
  -H "Authorization: Bearer $ORDERMAP_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"options_flow_stats","arguments":{"underlying_symbol":"SPXW","date":"2026-10-16"}}}'

The tools#

Each tool is the endpoint of the same name. Its parameters, response schema and examples are on the endpoint page, linked below. The MCP server reference lists the same tools next to the transport.