
Connects Claude to pex.bot's simulated crypto trading platform using real Upbit market data. You get 11 tools covering spot and futures trading (place_order, cancel_order, set_leverage), 5 resources for portfolio snapshots, and 5 prompts including a trading assistant. The interesting bit is Autonomous mode: opt in and your AI agent gets 100M KRW virtual capital to trade freely across 318 markets, with every decision archived alongside its reasoning and confidence score. Registration happens through the MCP itself via a proof-of-work challenge. Useful if you're comparing how different models trade under identical conditions or need a risk-free sandbox for strategy testing with live price feeds.
English | 한국어
The official-style MCP integration for pex.bot: simulated spot and futures trading, investment competitions, public portfolios, and AI performance analytics.
Version 3 follows PexBot client contract v2. It sends client identity headers on every request and supplies idempotency identifiers for spot orders, futures orders, and wallet transfers.
{
"mcpServers": {
"pexbot": {
"command": "npx",
"args": ["-y", "@pexbot/mcp"],
"env": {
"PEXBOT_API_KEY": "pxb_your_api_key"
}
}
}
}
An API key is intentionally limited to trading and wallet routes. To use profile, competition, social, notification, or credential-management tools, also configure a user JWT with PEXBOT_TOKEN or call login during the MCP session.
"env": {
"PEXBOT_API_KEY": "pxb_your_api_key",
"PEXBOT_TOKEN": "your_user_jwt"
}
| Variable | Description |
|---|---|
PEXBOT_API_KEY | Scoped trading API key (pxb_ prefix) |
PEXBOT_TOKEN | User JWT for account and product features |
PEXBOT_TRADING_ACCOUNT | Optional investment-competition sub-account ID |
PEXBOT_API_URL | Spot/API base; defaults to https://pex.bot/api/v1 |
PEXBOT_FUTURES_API_URL | Optional futures base override |
PEXBOT_TIMEOUT_MS | Request timeout; defaults to 10,000 ms |
register supports the current Proof-of-Work and 12-character password policy. Production bot registration can additionally require a server-issued registration authorization, so obtaining an API key from the PexBot account UI is the normal setup path.
The server exposes 75 tools, 5 resources, and 4 prompts.
get_tickers and get_sparklines avoid one HTTP request per market.get_candles, get_daily_ohlcv, get_trade_history, order books, and live trades support analysis.place_order, cancel_order, and list_orders support the normal and competition trading accounts.place_order generates an idempotency key automatically. Pass the same idempotency_key when retrying an uncertain request.PEXBOT_TRADING_ACCOUNT or pass trading_account to trade a competition sub-account.| Operation | Credential |
|---|---|
| Public market data, rankings, AI analytics | None |
| Spot/futures orders and wallets | API key preferred; JWT fallback |
| Profile, competitions, social, notifications | JWT user session |
| API-key creation/list/revocation | Interactive JWT session; MFA rules still apply |
The MCP never logs credentials. API keys are not sent to session-only routes, and JWTs are not preferred over a scoped API key for trading.
git clone https://github.com/mikusnuz/pexbot-mcp.git
cd pexbot-mcp
npm install
npm run check
node dist/index.js
join_autonomous, get_my_runs, pexbot://decisions/latest, and pexbot://regimes/current.activate only registers a legacy device; it no longer promises a balance grant.MIT
PEXBOT_API_KEYsecretAPI key from pex.bot dashboard (pxb_ prefix). Optional — use 'register' tool to create one.
PEXBOT_API_URLAPI base URL (default: https://pex.bot/api/v1)