Skip to main content
Glama
Polymarket MCP Server

Polymarket MCP Server

by yashhsm

Related Servers

Alternatives to Polymarket MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server for Polymarket prediction markets, providing real-time market data, prices, and AI-powered analysis tools for Claude Desktop integration.
      48
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      MCP server for Polymarket prediction markets enabling query of markets, events, narratives, arbitrage, and more via MCP or HTTP.
      9
      1
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      A read-only MCP server that lets Claude query Polymarket's public APIs for markets, events, live order books, price history, trades, open interest, trader leaderboards, and wallet positions and P&L. It also offers arbitrage scanning, market "x-ray" reports, calibration scoring, daily digests, and a local simulated paper-trading ledger — with no keys, no signer, and no real orders ever placed.
      23
      MIT
    • A
      license
      C
      quality
      D
      maintenance
      MCP server exposing 47 Polymarket API tools for AI assistants. Covers the full Gamma, CLOB, and Data APIs plus a fluent MarketBuilder for multi-source queries.
      47
      15 npm
      2
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Read-only MCP server for Polymarket prediction market data, enabling AI agents to search markets, get details, view holders, leaderboard, and user positions.
      49 PyPI
      MIT

    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