mcp-server-polymarket
Related Servers
Alternatives to mcp-server-polymarket
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables AI agents to discover and analyze prediction markets, execute trades, and manage positions on Polymarket via the Model Context Protocol.7106 npm20MIT
- AlicenseBqualityNot gradedmaintenanceEnables AI agents to interact with the Polymarket prediction market platform to discover markets, analyze real-time pricing, and monitor public portfolio data. It provides comprehensive access to market analytics, implied probabilities, and order books through the Model Context Protocol.5944 npm-
- FlicenseNot gradedqualityCmaintenanceEnables interaction with Polymarket prediction markets through read-only access to market data, events, orderbooks, and user positions, plus authenticated trading capabilities for creating and managing orders.1-
- AlicenseAqualityDmaintenanceProvides search, trending, odds, arbitrage, and category browsing for prediction markets (Polymarket & Kalshi) via the Model Context Protocol, enabling AI agents to access live market data without API keys.51MIT
- AlicenseBqualityDmaintenanceEnables LLM agents to interact with Polymarket prediction markets, including market discovery, real-time pricing, analytics, account management, and trading with built-in safety guards.34MIT
- AlicenseNot gradedqualityCmaintenanceProvides a comprehensive set of tools for Polymarket prediction market trading, including Gamma discovery, CLOB trading, gasless relayer, managed WebSockets, and paper simulation, enabling agents to interact with Polymarket natively.MIT
TDQS
Scored across 49 tools
Most tools target a distinct resource+action, and descriptions explicitly steer the agent (e.g. get_quotes vs get_order_books, list_markets vs list_order_book_markets, get_user_overview vs get_user_pnl). A few boundaries remain fuzzy: list_trades vs list_activity both return a wallet's trades, and list_positions vs list_combo_positions plus get_market vs get_market_trading_info vs get_live_activity require careful reading to choose correctly.
Overwhelmingly consistent snake_case verb_noun (get_*, list_*, search_docs/read_doc), with the perps family predictably prefixed. Minor deviations: the bare verb 'search' has no noun, and 'auth_status' is a noun phrase that breaks the verb_noun pattern.
49 tools is heavy even for a platform spanning Gamma, CLOB, Data API, Perps and docs, and several are marginal or niche (check_perps_invite_code, list_event_creators, get_live_activity, list_order_book_markets, search_docs/read_doc). The breadth is real but the surface feels like an API dump rather than a curated tool set.
Read coverage is excellent — markets, events, series, tags, positions, trades, order books, price history, perps and status are all covered. However the exposed surface has no order placement, cancellation or other write operations (auth_status hints at hidden write tools), leaving a significant gap for a trading platform.