openmm-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MEXC_API_KEY | No | API key for the MEXC exchange. | |
| BITGET_SECRET | No | Secret for the Bitget exchange. | |
| GATEIO_SECRET | No | Secret for the Gate.io exchange. | |
| KRAKEN_SECRET | No | Secret for the Kraken exchange. | |
| BITGET_API_KEY | No | API key for the Bitget exchange. | |
| GATEIO_API_KEY | No | API key for the Gate.io exchange. | |
| KRAKEN_API_KEY | No | API key for the Kraken exchange. | |
| MEXC_SECRET_KEY | No | Secret key for the MEXC exchange. | |
| BITGET_PASSPHRASE | No | Passphrase for the Bitget exchange. |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_tickerA | Get real-time price, bid/ask, spread, and volume for a trading pair on a supported exchange |
| get_orderbookB | Fetch order book depth (bids and asks) for a trading pair on a supported exchange |
| get_tradesC | Get recent trades for a trading pair on a supported exchange |
| get_balanceA | Get account balances for all assets (or a specific asset) on a supported exchange |
| list_ordersA | List open orders on a supported exchange, optionally filtered by trading pair symbol |
| create_orderB | Create a new order (limit or market) on a supported exchange |
| cancel_orderA | Cancel a specific order by ID on a supported exchange |
| cancel_all_ordersA | Cancel all open orders for a trading pair on a supported exchange |
| get_cardano_priceA | Get aggregated price for a Cardano native token from DEX liquidity pools (TOKEN/USDT via ADA bridge) |
| discover_poolsA | Discover Cardano DEX liquidity pools for a native token via Iris API |
| start_grid_strategyB | Calculate and optionally place grid trading orders around the current price |
| stop_strategyA | Cancel all open orders for a trading pair, effectively stopping any running grid strategy |
| get_strategy_statusA | Get current grid strategy status: open orders, current price, and P&L estimate |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| market_analysis | Analyze market conditions for a trading pair using ticker, order book, and recent trades data |
| portfolio_overview | Get a comprehensive overview of account balances and open orders across an exchange |
| grid_setup_advisor | Analyze market conditions and recommend optimal grid trading configuration |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| exchanges-list | |
| grid-strategy | |
| grid-profiles |
TDQS
Scored across 13 tools
Most tools have distinct purposes, such as create_order for order creation and get_ticker for price data. However, cancel_all_orders and stop_strategy both involve canceling orders for a trading pair, which could cause confusion in selection, though stop_strategy is tied to grid strategies.
The naming follows a consistent verb_noun pattern with snake_case throughout, such as get_balance and list_orders. Minor deviations exist, like discover_pools using 'discover' instead of 'get' or 'list', but overall the pattern is clear and readable.
With 13 tools, the count is well-scoped for a trading and strategy automation server. Each tool serves a specific function, from order management to price fetching and strategy control, without feeling excessive or insufficient for the domain.
The toolset covers core trading operations like order CRUD, balance checks, and market data, plus grid strategy management. A minor gap is the lack of tools for modifying existing orders (e.g., update_order) or detailed strategy configuration, but agents can work around this with the available tools.