Prediction Markets API MCP

The FinFeedAPI Prediction Markets API is available through a hosted Model Context Protocol (MCP) server at https://api.prediction-markets.finfeedapi.com/mcp. It exposes the API as self-describing tools, which makes it easy to use from MCP clients such as Cursor, Claude Desktop, or custom agent runtimes.

Use your regular FinFeedAPI API key in the X-APIKey header.

What is available through MCP?

The Prediction Markets MCP server currently exposes 14 tools grouped into four areas:

Typical discovery flow

Most integrations follow this order:

1. Call exchanges_list to discover supported venues such as POLYMARKET, KALSHI, MYRIAD, or MANIFOLD.
2. Call exchanges_get if you want venue metadata for one exchange.
3. Call markets_get_active for a compact list of active market_id values, or markets_get_history for fuller market objects with titles, descriptions, and prices.
4. Use activity_get_current or orderbook_get_current for the latest market state.
5. Call ohlcv_list_periods, then use ohlcv_get_latest_market or ohlcv_get_history_market for candles.
6. Use activity_get_trades_history, activity_get_quotes_history, or orderbook_get_history only when you need flat-file history and can keep the requested range narrow.

Live-tested notes

• markets_get_active returns only market IDs, not full market objects.
• ohlcv_get_latest_market returns rows in descending time order.
• ohlcv_get_history_market and ohlcv_get_history_exchange return rows in ascending time order.
• ohlcv_get_history_exchange requires both time_start and time_end, and the requested window cannot exceed 24 hours.
• Historical flat-file tools support either a full-day date query or a bounded time_start / time_end range.
• For low-activity markets, current activity calls may return sparse results or an explicit "no activity found" error.
• orderbook_get_current returns a snapshot with bids and asks, while orderbook_get_history returns raw order updates rather than reconstructed snapshots.

Start here