Skip to main content
Glama
Polymarket MCP Server

Polymarket MCP Server

by yashhsm

Polymarket MCP Server

A Model Context Protocol (MCP) server for seamless Polymarket integration

MIT License TypeScript Node.js

πŸš€ Overview

Polymarket MCP Server provides a comprehensive toolkit for accessing Polymarket data through the Model Context Protocol. This server enables seamless integration with Claude and other MCP clients, allowing you to search markets, fetch events, analyze leaderboards, query user activity, and much more.

Related MCP server: Polymarket MCP

✨ Features

  • πŸ“Š Market Search & Browsing - List and search Polymarket markets with advanced filtering, pagination, and sorting

  • πŸ“… Event Management - Discover and retrieve detailed information about Polymarket events

  • 🏷️ Tag System - Browse available tags for categorizing and filtering markets and events

  • πŸ† Leaderboard Data - Access trader rankings based on profitability and volume

  • πŸ‘€ User Analytics - Get detailed user activity including trades, splits, and merges

  • πŸ’Ό Wallet Analysis - Query trades and holdings for specific wallet addresses

  • πŸ“ˆ Market Insights - View top holders, open interest, and live volume data

  • πŸ” Full Search - Comprehensive search across markets, events, and profiles

πŸ› οΈ Available Tools

Market Tools

  • list_markets - List Polymarket markets with optional filtering by tags, pagination, and sorting

  • search_polymarket - Search Polymarket markets, events, and profiles using the public search API

  • get_market_by_slug - Fetch a specific Polymarket market by its slug identifier

Event Tools

  • list_events - List Polymarket events with optional filtering by tags, pagination, and sorting

  • get_event_by_slug - Fetch a specific Polymarket event by its slug identifier

  • get_live_volume - Get live volume data for a specific Polymarket event

Analytics Tools

  • get_open_interest - Get open interest data for Polymarket markets

  • get_top_holders - Get top holders for specified Polymarket markets

  • get_leaderboard - Fetch Polymarket trader leaderboard rankings (most profitable / highest volume traders)

User & Wallet Tools

  • get_user_activity - Get user activity from Polymarket including trades, splits, merges, and rewards

  • get_trades_by_wallet - Get all trades for a Polymarket wallet address using the public Data API

Category Tools

  • list_tags - List all available Polymarket tags for filtering markets and events

πŸ“¦ Installation

Prerequisites

  • Node.js (v18 or higher)

  • pnpm (or npm/yarn)

Setup

  1. Clone the repository

git clone https://github.com/yashhsm/polymarket-mcp.git
cd polymarket-mcp
  1. Install dependencies

pnpm install
  1. Build the project

pnpm build
  1. Start the server

pnpm start

πŸ”§ Usage

This MCP server can be used with any MCP-compatible client. Configure your client to connect to this server's stdio transport, and you'll have access to all available Polymarket tools.

Example: Using with Claude Desktop

Add this configuration to your Claude Desktop config file (typically located at ~/Library/Application Support/Claude/claude_desktop_config.json on macOS):

{
  "mcpServers": {
    "polymarket": {
      "command": "node",
      "args": ["/absolute/path/to/polymarket-mcp/dist/index.js"]
    }
  }
}

Note: Replace /absolute/path/to/polymarket-mcp with the actual absolute path to your cloned repository.

Example Queries

Once configured, you can ask Claude:

  • "Show me the top 10 trending Polymarket markets"

  • "What are the current odds for the 2024 election markets?"

  • "Who are the top traders on Polymarket this month?"

  • "Search for markets related to cryptocurrency"

  • "Show me live volume data for a specific event"

πŸ—οΈ Development

Building

pnpm build

Development Mode

Run with hot reload:

pnpm dev

Running Tests

pnpm test

Evaluation Mode

pnpm eval

πŸ“ Project Structure

src/
β”œβ”€β”€ index.ts              # Main MCP server setup and tool registration
β”œβ”€β”€ constants.ts          # Configuration constants and API endpoints
β”œβ”€β”€ eval.ts               # Evaluation utilities
β”œβ”€β”€ prompt-evals.ts       # Prompt evaluation functions
└── tools/                # Tool implementations
    β”œβ”€β”€ index.ts          # Tool exports
    β”œβ”€β”€ markets.ts        # Market-related tools
    β”œβ”€β”€ events.ts         # Event-related tools
    β”œβ”€β”€ leaderboard.ts    # Leaderboard tools
    β”œβ”€β”€ user.ts           # User activity tools
    └── ...               # Additional tool implementations

πŸ”Œ API Integration

This server integrates with the following Polymarket public APIs:

  • Markets API - For market data and search functionality

  • Events API - For event information and details

  • User API - For user activity and wallet data

  • Leaderboard API - For trader rankings and statistics

  • Data API - For trades, holders, and volume data

πŸ› οΈ Technology Stack

  • Node.js - JavaScript runtime environment

  • TypeScript - Type-safe JavaScript development

  • MCP SDK - Model Context Protocol SDK

  • Zod - Schema validation and type safety

🀝 Contributing

Contributions are welcome! If you'd like to contribute:

  1. Fork the repository

  2. Create a feature branch (git checkout -b feature/amazing-feature)

  3. Commit your changes (git commit -m 'Add some amazing feature')

  4. Push to the branch (git push origin feature/amazing-feature)

  5. Open a Pull Request

πŸ“„ License

This project is licensed under the MIT License - see the LICENSE file for details.

πŸ’¬ Support

For issues, feature requests, or questions:

πŸ™ Acknowledgments


Made with ❀️ by the Polymarket MCP community

Available Tools

15 tools
get_event_by_slugB

Fetch a specific Polymarket event by its slug identifier

Inputs: slug (required).

get_leaderboardB

Fetch Polymarket trader leaderboard rankings (most profitable / highest volume traders)

Inputs: user, limit, offset, orderBy, +3 more.

get_live_volumeB

Get live volume for a specific Polymarket event

Inputs: eventId (required).

get_market_by_slugB

Fetch a specific Polymarket market by its slug identifier

Inputs: slug (required).

get_open_interestC

Get open interest for Polymarket markets

Inputs: market, eventId.

get_top_holdersC

Get top holders for specified Polymarket markets

Inputs: market (required), limit, minBalance.

get_trades_by_walletC

Get all trades for a Polymarket wallet address using the public Data API

Inputs: walletAddress (required), side, limit, market, +3 more.

get_user_activityC

Get user activity from Polymarket including trades, splits, merges, and rewards

Inputs: user (required), limit, types, market, +2 more.

list_eventsC

List Polymarket events with optional filtering by tags, pagination, and sorting

Inputs: limit, order, closed, offset, +4 more.

list_marketsB

List Polymarket markets with optional filtering by tags, pagination, and sorting

Inputs: limit, order, closed, offset, +4 more.

list_tagsA

List all available Polymarket tags for filtering markets and events

Inputs: no named parameters.

search_polymarketC

Search Polymarket markets, events, and profiles using the public search API

Inputs: q (required), page, sort, cache, +10 more.

ws_get_orderbookA

Get live orderbook snapshot for a Polymarket asset via WebSocket. Returns current bids and asks.

Inputs: assetId (required), durationSeconds.

ws_subscribe_pricesB

Subscribe to real-time price updates for Polymarket assets via WebSocket. Collects price changes for specified duration.

Inputs: assetIds (required), durationSeconds.

ws_subscribe_tradesA

Subscribe to real-time trade updates for Polymarket assets via WebSocket. Collects trades for specified duration.

Inputs: assetIds (required), durationSeconds.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.5/5.0

    Scored across 15 tools

    Disambiguation4/5

    Most tools target clearly distinct resources/actions (markets, events, tags, holders, leaderboard, orderbook, trades). A few overlap: search_polymarket can return markets and events that list_markets/list_events also return, and get_user_activity (includes trades) overlaps with get_trades_by_wallet. Descriptions mostly clarify the boundaries, so confusion is limited.

    Naming Consistency4/5

    Nearly all tools follow a snake_case verb_noun pattern (list_markets, get_top_holders, get_event_by_slug). The ws_ prefix group is internally consistent but introduces a second convention, and search_polymarket uses a domain noun instead of a specific resource. Minor deviations, still highly predictable.

    Tool Count5/5

    15 tools sit at the top of the well-scoped range and each maps to a genuine capability (REST listing, slug lookups, search, analytics metrics, WebSocket streams). No redundant or filler tools are apparent for a read-only market-data server.

    Completeness4/5

    Coverage is strong for read-only analytics: markets, events, tags, search, holders, leaderboard, user activity, wallet trades, open interest, volume, and real-time streams. Minor gaps exist around historical price/candle data and any trading or comment operations, but core discovery and analytics workflows are covered.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers