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.

Get Started

View on GitHub

117

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

Install prerequisites

First, open a terminal on your machine:

  • 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

Then paste this command and press Enter:

# bash
1curl -LsSf https://astral.sh/uv/install.sh | sh

Skip if you already have them.

Step 2

Configure credentials

Now open a new terminal tab

  • MacOS — press Cmd + T
  • Windows (Windows Terminal) — press Ctrl + Shift + T
  • Linux — press Ctrl + Shift + T

The MCP prompts for your API key and secret. Create one at

→ Profile → API Keys (enable Read + Trade)

# bash
1uvx --from whitebit-mcp whitebit-mcp-setup --public=YOUR_API_KEY --secret=YOUR_SECRET_KEY

Want to try without an account? Skip this step — public market data works without credentials.

Step 3

Restart your AI tool

Start a new agent session

Step 4

Start trading

Ask Claude: Show my spot balance and buy 10 USDT of BTC at market price.

Full MCP docs

Full CLI docs

Software Development Kits

Simplify integration and save time to market

For AI clients

#MCP

#JSON-RPC

#Local-First

MCP Server

115 tools (spot, collateral, wallet, earn, sub-accounts) · Credentials passed per call, never stored · Works with all 5 clients

Secure WebSocket architecture

Automatic function discovery

Support for Claude Desktop & Cursor

MCP Server guide

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

CLI guide

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

Skills documentation

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

AI docs guide

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 Stay Local and Never Leave Your Machine: We Pass Credentials Directly to WhiteBIT so the AI Only Sees Results.

Security for autonomous trading. Local-first signing keeps keys on your machine — hidden from AI like Claude or Cursor.

Audit the source on GitHub

AI Tools FAQ

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. 100% local and free.

Get Started

Read the docs

FAQ

Keys are passed per call, never stored, logged, or cached. All processing happens locally. 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 self-hosted and executes trades/queries via the WhiteBIT API. The documentation MCP (hosted by Mintlify) 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.