MCP Server

The Adjacent MCP server exposes prediction-market data to AI agents over the Model Context Protocol. It is a view layer over the REST API: four task-shaped tools instead of one per endpoint, with chainable ids so an agent can discover an entity and then fetch its detail or price history.

Endpoint

1https://mcp.adjacent.markets/mcp

Public (no key) traffic uses the 15-minute-delayed snapshot tier. For realtime data, append your Adjacent API key as a query parameter (same key you use for the authenticated REST API):

1https://mcp.adjacent.markets/mcp?apiKey=YOUR_KEY

Generate and manage keys in account settings on adjacent.markets.

Connect an agent

Most agent hosts take a single URL under a "remote MCP" or "Streamable HTTP" option. Config file paths vary by host; paste one of these:

Cursor / Claude (remote Streamable HTTP)

1234567{
  "mcpServers": {
    "adjacent": {
      "url": "https://mcp.adjacent.markets/mcp"
    }
  }
}

With an API key (realtime tier)

1234567{
  "mcpServers": {
    "adjacent": {
      "url": "https://mcp.adjacent.markets/mcp?apiKey=YOUR_KEY"
    }
  }
}

Tools

Tool	When to use it
`list`	Browse what's tradable now (events by default), or list markets, indices, rates, or news, with search, sort, and pagination
`find`	Discover an entity by topic or name when you don't have an id yet. Optional `type` narrows to one kind (`index`, `rate`, `event`, `market`, `news`)
`get`	Full detail for one entity by id. Indices include constituents in a single call
`price`	Price history for an index, rate, market, or event. Pass a human timeframe (`24h`, `7d`, `30d`, `90d`); responses are a compact summary by default (`raw: true` for the full series). Events return per-child-market summaries

Ids from list / find chain into get / price: markets use <platform>:<raw> (for example kalshi:KXPRESPARTY-28-R); indices and rates use slugs such as red / pres.

MCP Server

Endpoint

Connect an agent

Tools

See also