Polymarket MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_marketsA | Retrieve Polymarket prediction markets with filtering and pagination options. Get market data including prices, volume, liquidity, and metadata. |
| get_eventsB | Retrieve Polymarket events which contain multiple related markets. Events group markets around a common theme or topic. |
| get_user_positionsB | Retrieve user's current positions in Polymarket prediction markets. Shows holdings, P&L, and position details. |
| get_user_activityC | Retrieve user's on-chain activity history including trades, splits, merges, redeems, rewards, and conversions. |
| get_market_pricesA | Get current market prices and trading data for specific markets or tokens. Shows bid/ask spreads, last traded prices, and market depth. |
| get_tradesA | Retrieve recent trades and trading history from Polymarket. Shows executed trades with prices, volumes, and market information. |
| get_order_bookC | Retrieve current order book data showing bids and asks for a specific market or token. Shows market depth and liquidity. |
| get_market_holdersB | Retrieve holders and their positions for a specific market. Shows who owns shares and their holding amounts. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool addresses a distinct aspect of Polymarket: markets, events, user positions, user activity, prices, trades, order book, and holders. No two tools have overlapping purposes.
All tools follow a consistent 'get_' prefix with a noun, making the verb_noun pattern predictable and clear.
8 tools cover the core read-only functionalities of a prediction market API without being excessive or insufficient.
The tool set covers market data, events, user positions, activity, trading history, order book, and holders. Missing write operations (e.g., placing bets) is acceptable for a read-only server, but a search or filter across all markets could be a minor gap.