Pmq (Polymarket CLOB V2) MCP Server

Most developer tooling work still happens through a UI a human drives. Pmq (Polymarket CLOB V2) MCP server moves it into the conversation instead. Fail-closed Polymarket CLOB V2 data and execution; trading tools gated behind PMQ_MCP_LIVE=1.

The short version

Fail-closed execution and market data for Polymarket CLOB V2, in Python, built agent-first. Local signing (your keys never leave your process), exchange-confirmed fills only, fee-correct math, deposit-wallet (POLY_1271) support that actually works in production, order-attribution registries (several bots can share one wallet, each with its own exchange-truth accounting), and a bundled MCP server: plug any LLM or agent framework that speaks MCP (Claude, ChatGPT, LangChain, your own loop) on top and it can read every market and, if and only if the operator enables it, trade under hard rails: tools that

• invalid amounts, the market buy orders maker amount supports a max accuracy
• no orders found to match with FAK order (HTTP 400, yet with an orderID):
• CLOB shows balance: 0 while your pUSD sits on-chain: the balance endpoint

Getting it running

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

The tools it exposes

The server publishes 14 tools. What each one is for:

• Situation — What pmq does
• signature_type — Wallet
• pmq_status — nothing
• find_markets — nothing
• event — nothing
• market — nothing
• market_snapshot — nothing
• book — nothing
• order_preview — nothing
• taker_fee — nothing
• account_collateral — paper mode, or keys
• account_trades — paper mode, or keys

What it needs from you

Configuration is passed through the environment: PMQ_MCP_PAPER, PMQ_MCP_LIVE, PMQ_MCP_MAX_USD, PMQ_MCP_DAILY_USD, POLY_PRIVATE_KEY, POLY_FUNDER, POLY_SIG_TYPE. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Things to watch

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Pmq (Polymarket CLOB V2).
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Pmq (Polymarket CLOB V2)'s toolset — Situation, signature_type, pmq_status and 11 more — is a fair guide to whether it matches your workflow. It is maintained by crp4222; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Pmq (Polymarket CLOB V2)'s own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.