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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_marketsA | Full-text search across Polymarket events and their markets. Returns matching events with each market's question, outcome prices, liquidity, and volume. Use this first to discover markets and their token IDs (token IDs feed get_orderbook / get_price_history). |
| get_marketA | Fetch full detail for a single market by numeric ID or slug, enriched with a live CLOB midpoint and spread for each outcome token. Use after search_markets when you need depth on one specific market. |
| get_orderbookA | Live bids/asks for one outcome token, with computed best bid, best ask, midpoint, and spread. Bids are returned highest-first and asks lowest-first (the top of book), truncated to |
| get_price_historyA | Historical mid-price time series for one outcome token. Returns summary stats (first/last/min/max, change) plus the raw points (Unix seconds |
| list_reward_marketsA | THE differentiator: lists markets currently paying maker (liquidity) rewards, ranked by daily reward pool ÷ in-band competition — i.e. where you earn the most rewards per dollar of resting liquidity. Each row includes the daily pool, max scoring spread, min order size, and the measured competition (notional resting within the scoring band). Credential-free. |
| get_trader_activityA | Public, read-only look at any wallet's Polymarket footprint — open positions, recent activity, or total portfolio value. Useful for whale-watching and copy-research. No credentials needed; uses only on-chain/public data. |
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 6 tools
Each tool has a clearly distinct role: search for discovery, get_market for single-market detail, get_orderbook for token order book depth, get_price_history for token history, list_reward_markets for reward-ranked opportunities, and get_trader_activity for wallet activity. The only potential overlap—market-level pricing from get_market versus token-level order book data from get_orderbook—is explicitly differentiated by scope and intended use.
All tool names use consistent snake_case with a clear verb_noun pattern: search_markets, get_market, get_orderbook, get_price_history, list_reward_markets, get_trader_activity. The verbs are standard and predictable across the set.
Six tools is well-scoped for a read-only Polymarket data and analytics server, covering discovery, detail, order book, history, rewards, and wallet activity without bloating the surface. Each tool earns its place by supporting a distinct read-only workflow.
The surface covers the core public-data workflows: market discovery, market detail, token order books, price history, reward-market ranking, and wallet activity. Minor gaps exist, such as no dedicated event-detail endpoint beyond search results and no market-level trade history endpoint, but agents can work around these with the provided tools.