agent-trade-kit MCP — Use Cases, Install & Live Demo

Name: agent-trade-kit MCP Server
Author: okx

Why use it

Key features

112 tools across 8 modules: market, spot, swap, futures, options, account, earn, bots
70+ technical indicators built in
Algo order types: conditional, trailing stops, grid, DCA
--read-only mode for research without trade execution
Credentials stored locally — no OKX-run cloud service

Live Demo

What it looks like in practice

agent-trade-kit.replay ▶ ready

0/0

Install

Pick your client

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "agent-trade-kit": {
      "command": "npx",
      "args": [
        "-y",
        "agent-trade-kit"
      ],
      "_inferred": true
    }
  }
}

Open Claude Desktop → Settings → Developer → Edit Config. Restart after saving.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "agent-trade-kit": {
      "command": "npx",
      "args": [
        "-y",
        "agent-trade-kit"
      ],
      "_inferred": true
    }
  }
}

Cursor uses the same mcpServers schema as Claude Desktop. Project config wins over global.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "agent-trade-kit": {
      "command": "npx",
      "args": [
        "-y",
        "agent-trade-kit"
      ],
      "_inferred": true
    }
  }
}

Click the MCP Servers icon in the Cline sidebar, then "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "agent-trade-kit": {
      "command": "npx",
      "args": [
        "-y",
        "agent-trade-kit"
      ],
      "_inferred": true
    }
  }
}

Same shape as Claude Desktop. Restart Windsurf to pick up changes.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "agent-trade-kit",
      "command": "npx",
      "args": [
        "-y",
        "agent-trade-kit"
      ]
    }
  ]
}

Continue uses an array of server objects rather than a map.

~/.config/zed/settings.json

{
  "context_servers": {
    "agent-trade-kit": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "agent-trade-kit"
        ]
      }
    }
  }
}

Add to context_servers. Zed hot-reloads on save.

claude mcp add agent-trade-kit -- npx -y agent-trade-kit

One-liner. Verify with claude mcp list. Remove with claude mcp remove.

Use Cases

Real-world ways to use agent-trade-kit

Research an asset before deciding to trade (read-only)

👤 Crypto traders doing due diligence ⏱ ~20 min advanced

When to use: You're considering a position and want charts + indicators + order book snapshot in one pass — without any risk of accidental trades.

Prerequisites

OKX API key (read-only scope) — OKX > API > Create key with read-only permission

Flow

Start in read-only mode

Configure agent-trade-kit with --read-only. Confirm trade tools are disabled.✓ Copied

→ Only research tools enabled
Pull data

For SOL-USDT: 4h candles last 30 days, RSI(14), MACD, current funding rate, top-of-book depth, and open interest trend.✓ Copied

→ Indicator stack
Synthesize

What's the short-term technical picture and is it aligned with funding/OI?✓ Copied

→ Analysis

Outcome: Informed view without execution risk.

Pitfalls

TA is not a prediction engine — Use as one input; not a trade signal on its own

Set up a grid bot within conservative parameters

👤 Crypto traders exploring grid strategies ⏱ ~30 min advanced

When to use: You want a range-bound grid on a pair you believe will oscillate.

Prerequisites

Funded OKX account — Real money at stake — tread carefully
Full API key (trade scope) — OKX > API; DO NOT enable withdrawal

Flow

Plan

For ETH-USDT spot: analyze last 30d range. Propose a grid: 40 levels, range $2800-$3400, $50 per grid investment. Show projected returns.✓ Copied

→ Grid plan with assumptions
Confirm and create

Before placing: confirm parameters. If I say 'go', create the grid bot; otherwise abort.✓ Copied

→ Explicit confirmation gate

Outcome: Grid bot running with sized risk.

Pitfalls

Range breakout = grid loses — Set a stop-loss price outside the range; review weekly
LLM mis-sizes the order — real money lost — Small starting sizes; verify every parameter before confirming

Check portfolio PnL and open positions

👤 Active traders ⏱ ~5 min intermediate

When to use: Morning check — what do I have open, how is it doing, any risks to my margin?

Flow

Pull account state

List all open positions (spot + swap + futures) with unrealized PnL. Show account equity + maintenance margin ratio.✓ Copied

→ Portfolio snapshot
Risk check

Which position is at highest liquidation risk? How far from its liq price?✓ Copied

→ Risk ranked

Outcome: Risk-aware morning check.

Combinations

Pair with other MCPs for X10 leverage

agent-trade-kit + filesystem

Log every trade execution locally for tax/audit

After each trade, append instrument/side/size/price/ts to ~/trades/YYYY-MM.csv.✓ Copied

Tools

What this MCP exposes

Tool	Inputs	When to call	Cost
market_candles	instrument, bar, limit?	Price data	1 API call
market_book	instrument, depth	Liquidity check	1 API call
account_balance		Account status	1 API call
spot_place_order	instrument, side, size, type, price?	Spot execution — destructive; confirm!	1 API call + real money
grid_bot_create	instrument, range, levels, total_investment	Launch a grid strategy — destructive; confirm!	1 API call + real money

Cost & Limits

What this costs to run

API quota: OKX API has per-endpoint rate limits
Tokens per call: Candles/books can be large — trim by limit
Monetary: Free MCP. Trades incur OKX fees + real money risk.
Tip: Use --read-only until you've read the tool list and trust your prompt discipline.

Security

Permissions, secrets, blast radius

Minimum scopes: API key with NO withdrawal permission, ever

Credential storage: Local via okx config init — stays on disk

Data egress: To OKX API; account data to your LLM provider

Never grant: Withdrawal permission on an API key used with an LLM

This MCP moves real money. Start in --read-only, then tiny sizes, then scale.
IP-whitelist your API key in OKX settings so a leaked key can't be used from elsewhere.
LLMs hallucinate numbers. Always confirm size, side, and instrument before execution.

Troubleshooting

Common errors and fixes

Signature invalid

API key/secret/passphrase mismatch. Re-run okx config init. Also check server clock (API is time-sensitive).

Insufficient balance for order

Transfer funds to trading account (OKX has multiple wallets).

Tool missing when expected

Per-module filtering may be blocking it; check config.

Alternatives

agent-trade-kit vs others

Alternative	When to use it instead	Tradeoff
Hummingbot / custom bot frameworks	You want non-LLM automated trading	Code, no LLM; more deterministic
Direct OKX API	You want full control and can self-audit	Build your own wrapper

More

Resources

📖 Read the official README on GitHub

🐙 Browse open issues

🔍 Browse all 400+ MCP servers and Skills