CCXT MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| cache-statsB | Get CCXT cache statistics |
| clear-cacheB | Clear CCXT cache |
| set-log-levelC | Set logging level |
| list-exchangesB | List all available cryptocurrency exchanges |
| get-tickerC | Get current ticker information for a trading pair |
| batch-get-tickersC | Get ticker information for multiple trading pairs at once |
| get-orderbookC | Get market order book for a trading pair |
| get-ohlcvC | Get OHLCV candlestick data for a trading pair |
| get-tradesC | Get recent trades for a trading pair |
| get-marketsC | Get all available markets for an exchange |
| get-exchange-infoC | Get exchange information and status |
| get-leverage-tiersC | Get futures leverage tiers for trading pairs |
| get-funding-ratesC | Get current funding rates for perpetual contracts |
| get-market-typesB | Get market types supported by an exchange |
| account-balanceC | Get your account balance from a crypto exchange |
| place-market-orderC | Place a market order on an exchange |
| set-leverageC | Set leverage for futures trading |
| set-margin-modeC | Set margin mode for futures trading |
| place-futures-market-orderC | Place a futures market order |
| get-proxy-configB | Get the current proxy configuration |
| set-proxy-configC | Configure proxy settings for all exchanges |
| test-proxy-connectionC | Test the proxy connection with a specified exchange |
| clear-exchange-cacheB | Clear exchange instance cache to apply configuration changes |
| set-market-typeC | Set default market type for all exchanges |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| exchanges |
TDQS
Scored across 24 tools
Most tools have distinct purposes, but there is some overlap between 'place-market-order' and 'place-futures-market-order', which could cause confusion if the agent doesn't understand the futures context. Additionally, 'clear-cache' and 'clear-exchange-cache' are similar, though the latter is more specific. Overall, descriptions help differentiate, but minor ambiguities exist.
Tool names follow a consistent verb_noun pattern with hyphens, such as 'get-ticker' and 'set-leverage', making them predictable and readable. However, there are minor deviations like 'batch-get-tickers' (which mixes verb order) and 'cache-stats' (which uses a noun-verb style), slightly breaking the pattern.
With 24 tools, the count is on the higher side but reasonable for a comprehensive crypto exchange server covering data retrieval, trading, configuration, and cache management. It might feel slightly heavy, but each tool appears to serve a specific function in the domain without obvious redundancy.
The tool set provides complete coverage for interacting with crypto exchanges, including market data (e.g., 'get-ohlcv', 'get-orderbook'), trading operations (e.g., 'place-market-order', 'set-leverage'), configuration (e.g., 'set-proxy-config'), and utility functions (e.g., 'cache-stats'). No significant gaps are apparent for the stated purpose.