OKX MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OKX_API_KEY | Yes | Your OKX API key | |
| OKX_API_SECRET | Yes | Your OKX API secret key | |
| OKX_API_PASSPHRASE | Yes | Your OKX API passphrase |
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 |
|---|---|
| get_account_summaryB | Get aggregated portfolio metrics |
| get_open_ordersB | Get all currently open orders |
| get_order_historyB | Get a list of filled orders for a given date range and optional symbol filter |
| get_portfolioA | Get a list of all assets in the account |
| get_positionsB | Get all derivative positions |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
The tools are mostly distinct, with each targeting a specific aspect of account or trading data (summary, open orders, order history, portfolio, positions). However, 'get_account_summary' and 'get_portfolio' could potentially overlap in providing aggregated asset information, which might cause slight confusion for an agent trying to choose between them for portfolio metrics.
All tool names follow a consistent verb_noun pattern with 'get_' prefix and snake_case (e.g., get_account_summary, get_open_orders). This predictable naming makes it easy for an agent to understand and navigate the tool set without ambiguity in style.
With 5 tools, the count is reasonable for a crypto exchange server focused on account and order management. It's slightly on the lower side but covers core functionalities well, though it might benefit from a few more tools for actions like placing or canceling orders to be fully scoped.
The tool set covers read-only operations for account data, orders, and positions, which is a good start. However, there are notable gaps in write operations, such as creating or canceling orders, and no tools for market data like ticker prices or order books, making the surface incomplete for full trading workflows.