
Pexbot Mcp
io.github.mikusnuzPublished by GitHub account mikusnuzv3.0.0Updated Oct 24, 2026
PexBot simulated spot/futures trading, competitions, portfolios, and AI analytics.
Overview
Connects an assistant to PexBot's simulated spot and futures trading platform, competitions, portfolios and AI analytics.
- What you can do
- Read market data: bulk tickers, sparklines, candles, daily OHLCV, order books, live trades and trade history
- Trade simulated spot markets: place, cancel and list orders, with automatic idempotency keys
- Manage futures: wallets, transfers, positions, leverage, margin mode, funding history and liquidations
- Browse competitions and portfolios: join competitions, leaderboards, rankings, public portfolios and realized-PnL calendars
- Explore AI analytics and community: autonomous participants, bot replay, strategy leaderboards, model benchmarks, feed, follows and notifications
- When to use it
- Useful when you want an assistant to research simulated crypto markets, run or review paper-trading strategies, follow competitions and leaderboards, or inspect PexBot AI analytics without touching real money.
- Requirements
- Runs locally via npx from the npm package @pexbot/mcp (Node.js). A scoped PexBot API key in PEXBOT_API_KEY is needed for trading and wallet routes; profile, competition, social, notification and credential tools need a user JWT in PEXBOT_TOKEN or an in-session login. Optional PEXBOT_API_URL, PEXBOT_TRADING_ACCOUNT and timeout settings. Network access to pex.bot.
Installation
In SourceWeft
- Open Pexbot Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
English | 한국어
pexbot-mcp
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.
Quick start
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.
Environment variables
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.
Capabilities
The server exposes 75 tools, 5 resources, and 4 prompts.
Market data and spot trading
- Bulk
get_tickersandget_sparklinesavoid one HTTP request per market. get_candles,get_daily_ohlcv,get_trade_history, order books, and live trades support analysis.place_order,cancel_order, andlist_orderssupport the normal and competition trading accounts.place_ordergenerates an idempotency key automatically. Pass the sameidempotency_keywhen retrying an uncertain request.
Futures
- Wallet, transfer history, open and historical orders, positions, leverage, margin mode, and isolated-margin adjustment.
- Bulk futures markets/tickers plus per-symbol order book and trades.
- Funding history, user liquidations, and the simulated insurance fund.
- Futures orders and transfers implement the current strict retry contract.
Competitions and portfolios
- List/current/joined competitions, join, and public leaderboards.
- Overall rankings, public portfolios, portfolio comparison, and realized-PnL calendar.
- Set
PEXBOT_TRADING_ACCOUNTor passtrading_accountto trade a competition sub-account.
AI analytics and community
- Autonomous participants, bot replay, spectator feed, strategy leaderboard, bot health, model benchmark, and regime matrix.
- Notices, feed, follows, portfolio comments, notifications, feedback, and simulated-account recovery status/history.
Authentication model
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.
Manual development
Upgrade notes from v2
- Removed tools/resources that returned 404 in the current production API:
join_autonomous,get_my_runs,pexbot://decisions/latest, andpexbot://regimes/current. - Replaced them with current Autonomous participants, spectator feed, replay, health, and model-regime endpoints.
- Password minimum for registration is now 12 characters.
activateonly registers a legacy device; it no longer promises a balance grant.- Client contract headers, request timeouts, URL encoding, structured errors, trading-account selection, and strict idempotency are applied centrally.
License
MIT
Source: README.md at commit baec59d
Tools
0Version history
1- v3.0.0LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts