agent_hub

Agent Hub MCP Server

agent_hub gives AI assistants access to Bitget market data, trading, and account operations through MCP. It serves users building exchange workflows, with selectable modules and a read-only mode for monitoring without trade or fund-movement actions.

Server facts

agent_hub MCP Server

Project

License
Not specified

Tech

Runtime / language
Not specified
Transports
stdio
Remote available
No
Authentication
Not specified

Activity

GitHub stars
231
Last commit
Data as of

Overview

Bitget spot and futures workflows are exposed to AI assistants through the bitget-mcp-server package in agent_hub. Public tools retrieve prices, order books, candles, trade records, funding rates, and open interest without credentials. Authenticated tools handle order placement and cancellation, execution records, futures positions, leverage, and trading configuration. Spot operations also include replacing orders and managing trigger orders. This lets an assistant work with both market observations and account-specific trading activity, while order-placement tools execute real trades.

Account workflows cover balances, bills, deposit addresses, transaction records, transfers, withdrawals, and subaccount administration. Private operations use an API key, secret key, and passphrase supplied together. Users can select which modules to expose or enable read-only mode, which removes write and trading operations, including transfers and withdrawals. A capability-discovery tool reports available modules for agent planning. The server communicates over stdio, with configuration examples for clients including Claude Desktop, Cursor, Codex, and VS Code. These controls support monitoring-only setups as well as authenticated trading and account workflows.

agent_hub setup notes

  • agent_hub records stdio only; confirm a network transport upstream before planning remote access.
  • agent_hub has no recorded license; confirm reuse terms in its repository.

Related MCP servers