Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@btse-mcpshow my open positions and wallet balance on testnet"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
btse-mcp
MCP server for the BTSE Futures API. Enables AI agents (Claude Desktop, Cursor, LangChain) to query market data, manage positions, and place orders on BTSE via natural language.
Prerequisites
Python 3.11 or higher — check with
python --versionpip — check with
pip --versionA BTSE account (testnet or live)
Step 1 — Get API keys from BTSE
Testnet (recommended first)
Register at https://testnet.btse.io
Go to Account → API tab → New API
Save the API Key and Passphrase — the passphrase is shown only once and is your
api_secretSet permissions: Read + Trading (add Transfer if needed)
Live
Same steps at https://btse.com
Step 2 — Install
pip install btse-mcp
# Verify
btse-mcp --helpMultiple Python versions (Anaconda etc): use the full path explicitly:
/usr/local/bin/python3.14 -m pip install btse-mcp
Step 3 — Configure accounts
Testnet
btse-mcp config --account-id testnet
# Prompts:
# API Key → paste your API key
# API Secret → paste your passphrase (input is hidden)
# Use testnet? [y/N] → y
# Verify the connection — should print BTC-PERP last price
btse-mcp test testnetLive (when ready)
btse-mcp config --account-id main
# Same prompts — answer 'n' to testnet
# See all configured accounts
btse-mcp listCredentials are stored encrypted at ~/.config/btse-mcp/accounts.enc.
Unified Futures Wallet: If your BTSE account has been upgraded to the Unified Futures Wallet (all accounts from late 2024 onwards), account endpoints automatically use the v2.2 API. No action needed.
Step 4 — Connect to Claude Desktop
btse-mcp install-claudeThis auto-writes the correct config for your OS and creates the file if it doesn't exist. Then restart Claude Desktop.
Manual alternative: if the command fails, add this to your config file directly:
OS
Path
macOS
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows
%APPDATA%\Claude\claude_desktop_config.jsonLinux
~/.config/Claude/claude_desktop_config.json{ "mcpServers": { "btse": { "command": "/full/path/to/btse-mcp", "args": ["start"] } } }Find the full path with:
which btse-mcp
Open a new chat in Claude Desktop — you should see a tools icon (🔧) in the input bar.
Test it:
"What is the BTC-PERP mark price on BTSE using account testnet?"
Step 5 — Connect to Cursor
Open Cursor → Settings → MCP → Add Server and enter:
{
"name": "btse",
"command": "btse-mcp",
"args": ["start"]
}Then use natural language in Cursor chat:
"Show my open BTSE positions" "Place a limit buy on BTC-PERP at 60000 size 1 using account testnet"
Alternative: run from source
# Clone the repo
git clone https://github.com/xbotlive/btse-mcp.git
cd btse-mcp
# Install in editable mode
pip install -e .
# Start
python -m btse_mcp startTool list
Tool | Description |
| Market summary for one or all symbols |
| Mark / index / last price |
| L2 orderbook snapshot |
| Recent public trade fills |
| OHLCV candlestick data |
| Historical funding rates |
| Futures wallet balance |
| Open positions |
| Maker / taker fee rates |
| Current leverage for a market |
| Place LIMIT / MARKET / OCO order (supports TP/SL) |
| Cancel by order ID, or cancel all for a symbol |
| List open orders |
| Single order detail |
| User trade history |
| Amend price / size / trigger price |
| Close position at market or limit |
| Set leverage (isolated or cross) |
| Get risk limit tier |
All tools accept an optional account_id parameter (defaults to "default").
Pass "account_id": "testnet" to route to your testnet account.
Multi-account usage
btse-mcp list # list all configured accounts
btse-mcp test main # test a specific accountIn prompts, specify the account explicitly:
"Using account testnet, show my BTC-PERP position"
Symbol naming
Use new-style perpetual names: BTC-PERP, ETH-PERP, SOL-PERP, etc.
Auth
BTSE uses HMAC-SHA384. The signature is:
HMAC-SHA384(api_secret, url_path + nonce + request_body)Sent via headers: request-api, request-nonce, request-sign.
See docs/integration.md for full details and worked examples.
Running tests
pip install pytest
pytest -vAuth signature tests run against the worked examples in the BTSE docs — no live API connection needed.
Troubleshooting
Problem | Fix |
| Run |
| Check API key and secret are copied correctly |
| Confirm testnet flag matches the account you created on |
Tools icon missing in Claude Desktop | Check JSON syntax in config file, restart Claude Desktop |
| Run |
| Your account uses the Unified Futures Wallet — the server auto-retries on v2.2, restart Claude Desktop |
| Restart Claude Desktop after any config or code change |
Disclaimer
Futures trading involves significant risk of loss. Always test on testnet before using live credentials.
Never commit API keys to version control — they are stored encrypted locally and excluded via .gitignore.
This server cannot be installed
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.