PMWallets copy-trading bot MCP server

Polymarket copy-trading bot (Node.js / TypeScript)

A ready-to-run Polymarket copy-trading bot built on PMWallets: it follows the traders you subscribe to and mirrors their fills on the Polymarket CLOB with your own account, inside the limits you set.

pmwallets-copytrade on npm · 中文说明 · Python version: polymarket-copy-trading-bot-python · SDK: pmwallets-node

What the bot does

win-rate confidence interval, profit without the single best market, activity and style, then subscribe.

1. You pick the traders on pmwallets.com: filter the board by the lower bound of the

block (measured latency). Missed frames are detected (session/seq) and replayed from the last fill handled, including everything that happened while the bot was down.

1. The bot receives every fill of those traders over the PMWallets WebSocket, typically within a second of the

machine; PMWallets never sees them and never places orders.

1. It mirrors them on Polymarket with your own account, inside the limits you set. Your keys never leave your

Quick start

# Node.js ≥ 20
npm install -g pmwallets-copytrade
pmwallets-copytrade init            # writes config.yaml
export PMW_API_KEY=pmw_...          # https://pmwallets.com/keys
pmwallets-copytrade run             # dry-run: logs every decision, trades nothing

When the dry-run log looks right, switch to live:

mode: live
polymarket:
  privateKey: ${POLY_PRIVATE_KEY}        # signs your orders
  signatureType: 3                       # see "Set up a Polymarket account for the bot"
  funderAddress: ${POLY_FUNDER_ADDRESS}  # your Polymarket profile address (holds the USDC)

pmwallets-copytrade status prints open positions, today's spend and any order still being confirmed. If the bot cannot establish by itself whether an order filled, it keeps the order's reservation (no further BUY can exceed your limits because of it) and asks you: check polymarket.com and run pmwallets-copytrade reconcile --none or --filled --usdc with the bot stopped. Every decision — including each skip and its reason — is appended to pmw-data/decisions..jsonl, and everything the bot prints also goes to pmw-data/bot..log.

Something went wrong? Run pmwallets-copytrade diagnose and email the pmw-diagnose-.json.gz it writes to support@pmwallets.com, with a line about what happened. The file has the bot's version, the check result, your config with the keys removed, the state files and the newest logs and decisions. It contains no private key or API key (they are removed by name, then by value from the whole file), but it does show your wallet addresses, the traders you copy, your trades and your machine's IP. Never send config.yaml or .env themselves.

How it decides

The rules come from a copy-trading bot that ran live on Polymarket; each one is there because of a lost trade or a rejected order.

Shortened. The full README is on GitHub.