Skip to main content
Use the published package @carbon-copy/polymarket-mcp as the default install path.

Claude CLI

Claude Desktop config

Add a local stdio server entry to your Claude Desktop MCP config:

Installed binary variant

If you prefer a globally installed executable:
Example config:

How the connection works

The package runs as a local MCP server over stdio. Your MCP client launches one of these commands:
  • npx -y @carbon-copy/polymarket-mcp
  • polymarket-mcp
No HTTP server is required for normal client integration.

Environment variables

@carbon-copy/polymarket-mcp can start with no secrets for public market discovery. Add credentials only for account, trading, rewards, relayer, or builder-relayer workflows.

Required for basic startup

  • None.

Common runtime variables (optional)

Auth variables (optional, feature-gated)

Public discovery tools work without auth. Auth-backed wrappers such as ensure_api_key, get_open_orders, place_order, get_rewards, and relayer execution flows require the relevant credentials.

Minimal smoke check

After connecting in your MCP client, run these in order:
  1. health_check
  2. list_markets with { "view": "simplified", "mode": "sampling" }
  3. search with { "q": "election", "limit": 5 }
  4. get_prices with { "items": [{ "token_id": "<token_id>", "side": "BUY" }] }
  5. read polymarket://status if your client supports resources
This verifies stdio transport, canonical market discovery, pluralized market-data tools, and runtime status visibility.

Local development only: run from source

Use a source checkout only when you need to inspect or modify the server locally.
For active development:
Use source checkout for local iteration, not as the default end-user install path.

Next steps