Bitget AI Agent MCP Server
Bitget crypto trading operations through natural-language commands for AI agents.
Data last scanned today · Reviewed today
Overview
The Bitget AI Agent MCP Server allows AI assistants such as Claude Desktop, Cursor, and Windsurf to interact directly with the Bitget Unified Trading Account (UTA/v3) API. By exposing 14 curated intent verbs rather than individual API endpoints, it enables users to execute complex trading operations using natural language. Functionality covers 89 trading operations, including spot and futures trading, account management, sub-account handling, and asset management. Built with TypeScript, the server is designed to provide a structured way for LLMs to interface with crypto market data and exchange features.
Our verdict
This server receives a security score of 35/100, indicating a high level of risk. Because it is community-maintained rather than official and lacks an editorially reviewed authentication mechanism, it is recommended only for experienced users who can audit the source code themselves. Please exercise caution when granting programmatic access to your crypto trading accounts.
- Supports 89 distinct trading operations via the Bitget UTA API.
- Utilizes a curated surface of 14 intent-based verbs.
- Small dependency footprint with only two direct dependencies.
- Maintained under an MIT open source license.
- Community-maintained project lacking official vendor verification.
- Authentication methods have not yet been editorially reviewed.
- Project security and read-only status lack comprehensive external audit.
Setup
{
"mcpServers": {
"agent-mcp": {
"args": [
"-y",
"@bitget-ai/bitget-agent-mcp"
],
"command": "npx"
}
}
}Paste into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), then restart Claude Desktop. Some servers require API keys or tokens as environment variables — check the project's README and add an "env" object if needed.
- No read-only mode — running this grants full read/write access.
- No built-in authentication — anyone with access to this config can invoke every tool it exposes.
Tools
| Tool | Description | Risk |
|---|---|---|
| discover | Provides progressive introspection of the surface, listing business domains, verbs, and tool schemas. | low |
| raw | Acts as an escape hatch that reaches any Bitget v3 API operation by operationId. | medium |
| market | Provides access to market data, ticker information, OHLCV/K-line history, and funding rates. | low |
| order | Manages spot and futures market orders, including placing and cancelling orders. | medium |
| position | Manages and retrieves information about active trading positions. | medium |
| strategy_order | Manages algorithmic or strategy-based trading orders. | medium |
| account_overview | Retrieves an overview of account balances and assets across accounts. | low |
| account_config | Updates account settings and configurations, such as leverage. | medium |
| repayment | Handles the repayment of loans or liabilities. | medium |
| transfer_funds | Executes internal transfers between different account types. | medium |
Compatibility
| Client | Local | Docker | Remote | Read-only |
|---|---|---|---|---|
| ChatGPT | ||||
| Claude Desktop | ||||
| Cursor | ||||
| VS Code | ||||
| Windsurf |
Frequently asked questions
›What are the system requirements for running the server?
You must have Node.js version 20 or higher installed on your machine. The server is compatible with macOS, Linux, and Windows.
›What permissions are required for the Bitget API key?
To perform trading operations, your Bitget API key must have both Read and Trade permissions enabled.
›Is it possible to use the server without providing trade access?
Yes, public market data operations do not require API credentials, as they function as read-only requests. Accessing account-specific information or executing orders, however, requires valid API keys.
›How can I prevent accidental trades during testing?
You can run the server with the --read-only flag to block all write operations, or use the --paper-trading flag to route requests to the Bitget demo environment.
›Does the server provide every API endpoint as a separate tool?
No, the server exposes 14 curated intent verbs instead of one tool per endpoint. This approach reduces context bloat and helps prevent tool-selection errors.
Badge
Maintain this server? Add the live badge to your README.