marketLABSCO SUMMARY
Real orders on a real exchange - so the two safety switches are the first thing to set.
An agent that can place a leveraged futures position is exactly as dangerous as it sounds. The project ships the right controls: paper trading for rehearsal, and a read-only startup flag that deletes the write tools rather than merely discouraging them. Decide which one you are in before you connect it, not after.
What it is
The entry point to a set of packages rather than a single server: an MCP server for desktop assistants, a CLI plus skills for terminal agents, a market-signal package that needs no account, an SDK, and an installer that sets up and upgrades them together.
What you get
- 89 Bitget UTA v3 operations, presented through 14 curated intent verbs rather than raw endpoints — two more, broker and inst_loan, load only when you name their institutional modules
- Spot orders, futures positions with leverage, internal fund transfers, batch cancels and an account overview
- Market analysis skills that need no account or API key - macro, on-chain intel, sentiment, technicals and a daily briefing
- Two meta tools, discover and raw, for exploring the operation surface and calling any operation by its ID
- A paper-trading mode for rehearsing before real funds are involved
- A read-only switch that removes every write tool at startup
Requirements
Node.js 20 or higher. A Bitget API key from the exchange's API management page for anything that touches your account; the market-signal package needs neither an account nor a key. The installer wires the packages into Claude Code, Codex and OpenClaw for terminal agents, while desktop assistants use the MCP package instead. The tools deliberately do not read .env files, so credentials must be passed the way each package documents.
Setup effort
One command plus a key — npx -y @bitget-ai/bitget-agent-mcp, then supply credentials
USE CASES
01
Trading by describing the trade
Say what you want in a sentence - a spot buy, a leveraged long, a transfer between accounts - and let the intent verb map it to the right operation.
02
Watching the market without handing over an account
Install the signal package on its own; the sentiment, macro and technical skills read public data and need no key at all.
03
Practising before risking funds
Create a demo API key and run in paper-trading mode, so the same instructions execute against nothing real.
04
Letting an agent look but not touch
Start with the read-only flag; the write tools are removed from the surface, so the model cannot see or call them.
18 tools
Listed in project docs. Your client may show a different list.
orderpositionstrategy_orderaccount_overviewaccount_configrepaymenttransfer_fundsdepositwithdrawfunds_recordssubaccountloantaxbrokerinst_loandiscoverrawBEFORE YOU INSTALL
What to know first
Tools you get
18 tools named in the project's documentation.
Requires
- npx on PATH
- BITGET_API_KEY in your environment
- BITGET_SECRET_KEY in your environment
- BITGET_PASSPHRASE in your environment
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y @bitget-ai/bitget-agent-mcpMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"bitget": {
"command": "npx",
"args": [
"-y",
"@bitget-ai/bitget-agent-mcp"
],
"env": {
"BITGET_API_KEY": "<YOUR_BITGET_API_KEY>",
"BITGET_SECRET_KEY": "<YOUR_BITGET_SECRET_KEY>",
"BITGET_PASSPHRASE": "<YOUR_BITGET_PASSPHRASE>"
}
}
}
}<YOUR_BITGET_API_KEY>, <YOUR_BITGET_SECRET_KEY> and <YOUR_BITGET_PASSPHRASE> come from Profile → API Management on bitget.com. Restart Claude Desktop afterwards. Without them only public market data works. Add "--read-only" or "--paper-trading" (with a Demo API key) after the package name in args to block trades or use Bitget's Demo environment.
Cursor
In Cursor Settings → MCP, click Add New Server.
Command:
CURSOR · TERMINAL
npxArgs: -y @bitget-ai/bitget-agent-mcp
Env: BITGET_API_KEY, BITGET_SECRET_KEY and BITGET_PASSPHRASE, set to your Bitget API Key, Secret Key and Passphrase.
