Polymarket MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| POLYMARKET_KEY_ID | No | API key ID for authenticated trading. Get at https://app.polymarket.com/api-keys | |
| POLYMARKET_SECRET_KEY | No | API secret key for authenticated trading. |
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 |
|---|---|
| search_polymarketA | Search Polymarket markets by keyword. Returns matching events with their markets, odds, and volume. Use this to find slugs for other tools. |
| get_polymarket_marketA | Get full details for a specific Polymarket market by slug. Includes current odds, outcomes, volume, liquidity, and order book. |
| get_polymarket_trendingA | Get trending Polymarket events ordered by volume. Good for discovering popular markets. |
| get_polymarket_priceA | Get current odds for a specific market by slug. Shows all outcomes with implied probability. |
| get_polymarket_bet_analysisA | Full bet analysis: current odds, implied probability, potential profit on a $100 bet, vig estimate, and value assessment. |
| get_polymarket_eventsA | List Polymarket events (groupings of related markets). Good for browsing by category like politics, sports, crypto. |
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 function: analysis, event listing, market details, price, trending, and search. No overlapping purposes.
All tools use a consistent 'get_' or 'search_' prefix followed by the domain name 'polymarket' with underscore-separated words, making them predictable.
Six tools is optimal for a prediction market server, covering browsing and analysis without being too sparse or overly numerous.
The tools cover key operations: listing, searching, getting details, pricing, trending, and analysis. However, actions like placing bets or managing accounts are absent, which might limit full workflow integration.