WhiteBIT AI Tools
Trade with AI. 115 tools. Your rules
Connect Claude, Cursor, and 3 other AI clients directly to the WhiteBIT API. Execute trades and analyze markets using natural language.
115
MCP Tools
112+
CLI Commands
5
AI Clients
2.0
Apache License
Works with your favorite AI
Any MCP-compatible client works out of the box.
Step 1
Create API keys
Go to whitebit.com → Profile → API keys → Create key. Enable Read and Trade. Leave Withdraw disabled. Copy both values — the public and private key are needed on the next step.
Only need public market data — prices, order book, candles? Skip this step and leave the keys out on step 2.
Step 2
Connect Claude Code
Open your terminal:
- MacOS — press Cmd + Space, type Terminal, press Enter
- Windows — press Win + R, type powershell, press Enter
- Linux — press Ctrl + Alt + T or search for Terminal in your apps
Paste the command below and replace the two placeholders with your own keys.
Don't have an account yet? Run the command without the two --header lines — public market data works without keys. --transport http is required — without it Claude Code will try to run the URL as a command. -s user makes the server available across all your projects and keeps keys out of repos.
Step 3
Restart your AI tool
Exit the current session and run claude again. To verify, run claude mcp list — whitebit-mcp should show as connected.
Step 4
Start trading
Ask Claude: Show my spot balance and buy 10 USDT of BTC at market price.
Software Development Kits
Simplify integration and save time to market
For AI clients
#MCP
#JSON-RPC
#Hosted
MCP Server
115 tools (spot, collateral, wallet, earn, sub-accounts) · Credentials sent as request headers on every call, never stored · Works with all 5 clients
Secure WebSocket architecture
Automatic function discovery
Nothing to install — connect over HTTPS
For terminals & scripts
#CLI
#npm/brew
#JSON
#Automation
Native CLI
High-performance terminal client for manual and scripted operations. Management of keys and bulk order execution.
Low-latency execution path
Local encryption of API credentials
Comprehensive command suite
For analysis & signals
#Skills
#No server
#Natural language
Skills
Market intelligence (macro, on-chain, institutional) · Technical analysis — EMA, RSI, MACD, 20+ indicators · Sentiment & signals
Market intelligence — macro, on-chain
Technical analysis — EMA, RSI, MACD
Sentiment & signals — fear/greed
For exploring the docs
#Docs MCP
#No setup
#Read-only
AI Docs
Covers REST v1/v2/v4, WebSocket, OAuth · Hosted by WhiteBIT — no setup required · Works alongside the trading MCP in the same session
Covers REST v1/v2/v4, WebSocket, OAuth
Hosted by WhiteBIT — no setup required
Works alongside the trading MCP
Engineered for Complexity
From Deep Analysis to Instant Execution
Market Data
No API key
Get last 1H candles for WB/USDT and calculate EMA
Spot Trading
API key
Buy 100 USDT worth of SOL if price drops below 150
Collateral Tools
API key
Check current leverage ratio for open BTC position.
Asset Search
No API key
Check current leverage ratio for open BTC position.
Order Audits
API key
List all cancelled orders from the last 48 hours
Balance Sync
API key
Aggregate balances across main and trade accounts
Fee Analysis
API key
Calculate total trading fees paid this month in WB
Earn & Lending
API key
Show my active staking plans
Your Keys Go Straight to WhiteBIT and Nowhere Else: the AI Only Ever Sees the Results.
Security for autonomous trading. Your keys go to WhiteBIT over HTTPS and are never shared with the AI provider — Claude and Cursor only receive the response data.
The AI provider receives tool outputs — not credentials
API keys are passed directly to WhiteBIT at call time. Claude, Cursor, and every other client only ever see the response data — never the key itself.
The server stores nothing
No keys, no trade history, no session data is written to disk. Each call is stateless. Restart the server and nothing persists.
Isolate exposure with a sub-account
Create a dedicated WhiteBIT sub-account for AI tool access. Scoped permissions, separate balance, independent API key — the main account is untouched.
Read the code
The MCP server and CLI are fully open source under Apache 2.0. Every line that handles credentials is public on GitHub.
Stop coding. Start trading.
115 AI tools ready in 60 seconds. No install, free to use.
FAQ
Keys are sent as request headers on each call and are never stored, logged, or cached. They go only to WhiteBIT. Open source code allows for full auditing.
No storage, logging, or caching of credentials occurs. This is verifiable in the public source code.
No. Recommendation is to use API keys with the minimum permissions required (Read/Trade). Withdrawal permissions should be disabled for safety.
Claude Code, Cursor, Claude Desktop, Codex, and OpenClaw are fully supported.
No. Public market data queries work without an API key using the 'public' role. Trading and private account data require a WhiteBIT account and API keys.
The trading MCP is hosted by WhiteBIT and executes trades and account queries via the WhiteBIT API. The documentation MCP is for searching and querying documentation.
Rate limits match the standard WhiteBIT API limits. See the API documentation for specific tier details.
Yes. The CLI supports --json output, --dry-run mode, and exit codes for seamless automation.
The WhiteBIT API supports WebSockets. The MCP server and CLI primarily utilize REST endpoints for stateless tool calls.
The tools are free and open source under the Apache 2.0 license. Standard exchange trading fees apply to executed orders.
