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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_marketsA | Search events and markets by free-text keyword. Use this as the primary discovery tool when the user names a topic but not an event/market ID. Matches against event titles, market questions, and descriptions.
Returns a list of event dicts with nested markets. Key fields:
Does NOT include |
| get_active_marketsA | Browse active (open, unresolved) events sorted by a field. Use this for discovery when the user asks "what's hot / most liquid /
expiring soon" without naming a topic. For keyword search, use
Returns a list of event dicts with nested markets. Each event has Does NOT include event-level |
| get_eventA | Get one event with all of its nested markets. Use when the user cares about a whole topic (all candidates, all strike
brackets, etc.). For one specific sub-question, use
Returns the event dict with its full
Does NOT include per-market |
| get_marketA | Get full details for one market, including order-book edges and momentum. Use when the user cares about a single specific question (one candidate's
odds, one strike price). For the whole topic, use
Returns a single market dict. Notable fields:
|
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 4 tools
Each tool targets a distinct purpose: browsing active markets, retrieving a full event, getting detailed market info, and searching by keyword. No functional overlap exists.
All tool names follow a consistent verb_noun snake_case pattern: get_active_markets, get_event, get_market, search_markets. The verbs are fitting and predictable.
With 4 tools, the scope is appropriately focused on data retrieval for prediction markets. It's slightly lean but covers the core use cases without being overwhelming.
The tool set covers essential discovery and detail retrieval for events and markets. Minor gaps exist (e.g., no history or category listing), but the core workflow is well-supported.