Polytrader2Polytrader2
Open-source Polymarket desktop client

Polytrader2

Fast local desktop trading app. Open source custody. MCP-powered AI agents for strategy and bot automation.

Fast
Instant market and account data.
Secure
Local keys. Open code.
Automated
AI strategies. Trading bots.

Features

Built for fast, secure, automated trading

Polytrader2 keeps data, keys, and strategy execution local, while connecting AI agents through MCP.

Local cache and auto sync

Market, account, order, and position data are cached locally and kept up to date automatically, so common actions respond fast.

System-protected keys

Keys are encrypted by the operating system, using DPAPI on Windows and Keychain on macOS.

Local strategy VM

Strategies run locally inside an isolated VM with controlled access to app capabilities and trade actions.

MCP for AI agents

Connect Claude Code, Codex, and other AI agents to market context and strategy workflows through the built-in MCP Server.

Demo

See the full workflow

From fast market browsing and local wallet records to AI-assisted strategy writing and bot execution, this section is ready for the product demo video.

Fast browsing after local sync
MCP for Claude Code and other local AI agents
Strategy runs, logs, and order records
Polytrader2 demo video

MCP

MCP setup guide

Polytrader2 exposes a local HTTP MCP server. The default endpoint is http://localhost:8708/mcp and requests are protected with a Bearer token.

Before connecting
Enable the MCP service in Polytrader2 settings
Confirm the endpoint is http://localhost:8708/mcp
Copy the MCP token generated by Polytrader2
Claude Code

Run this command in your terminal to add Polytrader2 as a user-scoped MCP server.

polytrader2-mcp
$
claude mcp add --transport http --scope user polytrader2 http://localhost:8708/mcp \
  --header "Authorization: Bearer <YOUR_MCP_TOKEN>"
In Claude Code, run /mcp and confirm polytrader2 is connected.

Strategy

Turn strategies into runnable, reviewable bots

Polytrader2 is designed for real trading workflows: use local AI agents to help draft strategies, bind them to markets and wallets, then let the desktop app run, record, and contain execution.

Safety boundaries
Private keys stay out of strategies

Strategies receive account summaries and host-managed trading capability, while key material remains under local desktop custody.

Isolated execution

Strategies run in an isolated VM child process and cannot freely access the desktop app, database, or system environment.

Explicit trading path

Orders and cancellations go through the desktop trading service and are written to order records.

Open-source verification

The execution boundary, account handling, and order recording logic can be inspected in the source code.

Strategy workflow

Local market context

Strategies use locally synced markets, order books, trades, orders, and positions, reducing repeated waits on remote APIs.

AI-assisted writing

MCP gives Claude Code or Codex market context, so local AI agents can help draft, revise, and explain trading strategies.

Bot execution

A strategy can be bound to a specific market, outcome, and account, then run as a bot that reacts to data changes.

Reviewable history

Starts, stops, logs, errors, and order requests are recorded locally for review and debugging.