Kraken CLI MCP Server

Name: Kraken CLI MCP Server
Author: Kraken

Kraken's own trading CLI served as a local stdio MCP server for market data, balances and live or paper orders

Official · Kraken Rust Local · stdio Finance and payments

GitHub Website

43 popularity score ★ 804

Connect your client

Local (from source)

Add in one click

Add to Cursor Add to VS Code Add to LM Studio

Opens the app, which asks before it adds the server.

Or add it by command or config

FirstTerminal

cargo install --locked --git https://github.com/krakenfx/kraken-cli kraken-cli

Claude CodeTerminal

claude mcp add kraken-cli -- kraken-mcp -s 'market,paper,feedback'

Claude Desktopclaude_desktop_config.json

{
  "mcpServers": {
    "kraken-cli": {
      "command": "kraken-mcp",
      "args": [
        "-s",
        "market,paper,feedback"
      ]
    }
  }
}

Cursor~/.cursor/mcp.json

{
  "mcpServers": {
    "kraken-cli": {
      "command": "kraken-mcp",
      "args": [
        "-s",
        "market,paper,feedback"
      ]
    }
  }
}

VS Code.vscode/mcp.json

{
  "servers": {
    "kraken-cli": {
      "type": "stdio",
      "command": "kraken-mcp",
      "args": [
        "-s",
        "market,paper,feedback"
      ]
    }
  }
}

Codex~/.codex/config.toml

[mcp_servers.kraken-cli]
command = "kraken-mcp"
args = ["-s", "market,paper,feedback"]

Gemini CLITerminal

gemini mcp add --scope user kraken-cli kraken-mcp -- -s 'market,paper,feedback'

Settings 10

Set together: spot key
`KRAKEN_API_KEY` secret	Optional: Spot API key. market and paper tools work without it. For account, trade, funding, earn and subaccount tools.
`KRAKEN_API_SECRET` secret	Optional: Secret for the spot API key.
Set together: futures key
`KRAKEN_FUTURES_API_KEY` secret	Optional: Futures API key, a separate key from the spot one. For live futures tools.
`KRAKEN_FUTURES_API_SECRET` secret	Optional: Secret for the futures API key.
`KRAKEN_WORKSPACE`	Optional: Workspace to scope paper and session state to. For workspace, paper and session tools.
`KRAKEN_SPOT_URL`	Optional: Spot REST base URL, https and Kraken hosts only. Default `https://api.kraken.com`.
`KRAKEN_FUTURES_URL`	Optional: Futures REST base URL. Default `https://futures.kraken.com/derivatives/api/v3`.
`KRAKEN_FEEDBACK_ENDPOINT`	Optional: Where feedback uploads go. Default `https://cli-feedback.kraken.com/v1/feedback`. For kraken_feedback.
`KRAKEN_AGENT_CLIENT`	Optional: Client name sent in request headers, instead of the one detected from the environment.
`KRAKEN_INSTANCE_ID`	Optional: UUID sent as the install ID, instead of the one stored in the config folder.

What it does

Kraken publishes kraken-cli, a Rust command-line tool for its exchange, and since version 0.5.0 the install also drops a separate kraken-mcp binary next to it. That binary is the MCP server. Your client starts it over stdio, and it turns CLI commands into tools named kraken_ plus the command, so kraken_ticker runs what `kraken ticker` would. Calls go through the CLI's own code, which means errors arrive as the same JSON envelopes, with retry hints when Kraken rate-limits you.

Which tools show up depends on -s. Started bare it loads market, account, paper, workspace and feedback. market and the two paper groups work with no key at all. account needs a key and is mostly reads. trade, futures, funding, earn and subaccount can place and cancel real orders, withdraw, stake and move money, so you have to ask for them by name or pass -s all. With every group loaded the repo's pinned test snapshot lists 152 tools, out of the 188 commands in its catalog. There is a research side too. You can try a paper strategy in a workspace and judge it with lab experiments built on recorded sessions before any real funds move.

The key it signs with can be one you paste in, or one the CLI made for you when a person ran `kraken auth login` in a terminal and approved access in the browser. The server picks up that stored key, but it never offers the login itself as a tool.

Tools that move money are flagged dangerous. Unless you start it with --allow-dangerous, the server asks you to approve each such call through MCP elicitation. Kraken calls the CLI experimental and the MCP part alpha.

What it needs

Runtime	Rust 1.97+
Runs on	macOS, Linux
Kraken	FreeOnly for account and live trading tools. Market data and paper trading need no account

Kraken's installer script or a release binary puts kraken, kraken-mcp and kraken-shell in ~/.cargo/bin with no Rust needed. Building from source needs Rust 1.97 or later. Windows works only through WSL. For account and live spot tools, run `kraken auth login` once in your own terminal: it opens Kraken in the browser, you approve within 5 minutes, and it stores a restricted spot key in config.toml (no withdrawals, 90 days at most, --read-only for one that cannot trade). Over SSH, forward ports 27461 to 27463 and add --no-browser. Or create an API key pair on Kraken and pass it as KRAKEN_API_KEY and KRAKEN_API_SECRET. Futures tools always need their own futures key pair.

Limits

Not covered Streaming groups (websocket, futures-ws), recording, replay and the setup wizard stay CLI-only: 152 of the 188 catalog commands are MCP tools
Limit OAuth sign-in (kraken auth login) is not served over MCP and refuses to run without a terminal, so a person has to run it first
Limit When the OAuth sign-in key expires, account and trade tools return an auth error. The CLI does not fall back to another stored key
Early release Kraken labels the software experimental and the MCP integration alpha
Platform Builds for macOS and Linux only. Windows needs WSL
Region xStocks are not offered in the USA, and which products you can use varies by country
Limit On a client without MCP elicitation, a dangerous call runs as soon as the model sets acknowledged=true
Rate limit No client-side throttling: Kraken's rate-limit rejections come back as errors with a retry suggestion
Limit A source install over an older one that had kraken-mcp or kraken-shell stops with "binary already exists" until you run cargo uninstall kraken-mcp kraken-shell or add --force
Limit The stdio command is kraken-mcp from v0.5.0 on. Older pages and installs start it as kraken mcp

Streaming groups (websocket, futures-ws) are not exposed over MCP, nor are recording, replay and other long-running CLI features. Runs over stdio only, with no hosted endpoint. The setup tools kraken_auth_set and kraken_auth_reset are kept out of MCP. xStocks are not offered in the USA and product availability varies by country. Kraken calls the software experimental and the MCP part alpha. Its skill guide warns that clients cope best with 50-100 tools, so -s all may be too many for some clients.

Who it suits

Suits someone with a Kraken account who wants an assistant to read prices, check balances or test paper strategies on their own Mac or Linux box, using the exchange's own code rather than a third-party wrapper. Leaving the groups at market and paper needs no key and cannot touch funds. Adding trade, funding or earn hands the assistant real money, which only makes sense with a tightly scoped key and a client that shows approval prompts. If you trade elsewhere, want a hosted server, or run Windows without WSL, look at other options.

Tools 56 of 152

30 only read, 23 change things, 3 can delete or overwrite.

kraken_ticker: Last price, bid, ask and 24h volume for one or more pairs
kraken_orderbook: Order book depth for a spot pair
kraken_ohlc: Candles (open, high, low, close) for a pair and interval
kraken_trades: Recent public trades on a pair
kraken_pairs: Tradable spot pairs and their rules
kraken_assets: Asset list with names and precision
kraken_status: Exchange system status
kraken_server_time: Kraken's server clock
kraken_tape_list: Recorded market-data tapes kept on this machine
kraken_balance: Balances held in the spot account
kraken_trade_balance: Margin and equity summary for the account
kraken_open_orders: Orders still open on the account
kraken_closed_orders: Filled and cancelled orders
kraken_trades_history: Your own past fills
kraken_ledgers: Ledger entries for deposits, trades and fees
kraken_export_delete deletes: Delete a requested account export report (dangerous)
kraken_order_buy changes: Place a live spot buy order (dangerous)
kraken_order_sell changes: Place a live spot sell order (dangerous)
kraken_order_amend changes: Change price or size of an open order (dangerous)
kraken_order_cancel changes: Cancel one open order (dangerous)
kraken_order_cancel_all changes: Cancel every open spot order (dangerous)
kraken_withdraw changes: Send funds out to a saved withdrawal address (dangerous)
kraken_deposit_methods: Ways an asset can be deposited
kraken_deposit_addresses: Deposit addresses for an asset
kraken_wallet_transfer changes: Move funds between spot and futures wallets (dangerous)
kraken_earn_strategies: Staking and earn products on offer
kraken_earn_allocate changes: Put funds into an earn strategy (dangerous)
kraken_earn_deallocate changes: Take funds out of an earn strategy (dangerous)
kraken_subaccount_transfer changes: Move funds between master and subaccounts (dangerous)
kraken_futures_tickers: Prices for all futures contracts
kraken_futures_positions: Open futures positions
kraken_futures_order_buy changes: Open or add to a live futures long (dangerous)
kraken_futures_order_sell changes: Open or add to a live futures short (dangerous)
kraken_futures_cancel_all changes: Cancel all open futures orders (dangerous)
kraken_futures_set_leverage changes: Set the margin multiplier on a futures market (dangerous)
kraken_paper_init changes: Start a simulated spot account with a chosen balance
kraken_paper_buy changes: Simulated buy filled against live prices
kraken_paper_sell changes: Simulated sell filled against live prices
kraken_paper_status: Value and profit of the simulated account
kraken_paper_reset deletes: Wipe the simulated account (dangerous)
kraken_futures_paper_buy changes: Simulated futures long against live prices
kraken_futures_paper_positions: Positions held in the simulated futures account
kraken_explain_pnl: Break down profit and loss for a recorded session
kraken_workspace_create changes: Create an isolated paper or live workspace
kraken_workspace_report: Report on a workspace's sessions and results
kraken_workspace_promote changes: Promote a workspace (dangerous)
kraken_workspace_reset deletes: Clear a workspace's state (dangerous)
kraken_session_note changes: Attach a trade rationale to the current session
kraken_session_show: Fills, notes and results of one session
kraken_lab_new changes: Set up a research experiment with fixed pass criteria
kraken_lab_score: Score an experiment against its criteria
kraken_lab_compare: Compare the sessions of an experiment
kraken_lab_next: Suggest the next step for an experiment
kraken_feedback changes: Upload a text note to Kraken's feedback service
kraken_auth_show: Which stored or env key is active, without the secret
kraken_auth_test: Check that the configured API key works

Popularity

43 popularity score, on our list (the bar is 36)

★ 804

GitHub stars	804	34.9 points
Official server	Yes	8 points

Measured 2026-11-08. How the score works.

Where it is published

Code	krakenfx/kraken-cli ★ 804

What it can reach

Runs	On your machine
Reaches	The internet, Your account at a service, Money or payments, Files on your machine
Changes things	Yes: it can write, send, create or delete
Sign-in	An API key or token
Licence	MIT (GitHub)
Usage data	Sends it Every REST and WebSocket request to Kraken carries headers with the CLI version, the detected agent client and a random install ID kept in the config folder
Latest version	0.5.1 GitHub release, 2026-10-29
Last code change	2026-10-29

Nothing is hosted. It runs on your machine over stdio and calls Kraken's REST APIs with your key's permissions, so any connected agent acts as that account. A key from `kraken auth login` covers spot only and cannot withdraw. One you create yourself carries whatever rights you gave it. With trade, futures, funding, earn or subaccount loaded it can place orders, stake and move funds. Guarded mode is the default: each dangerous call waits for your approval through MCP elicitation, and a client that cannot show that prompt lets the call run once the model passes acknowledged=true. --allow-dangerous drops both checks. Keys come from flags or environment variables, else config.toml (created 0600). The default feedback group uploads text you give it to Kraken. Kraken warns against tunnelling it.

Over time

GitHub stars 804 +48 (+6 %)

804756

14 Oct 20268 Nov 2026

Popularity score 43 +0 (+1 %)

4343

14 Oct 20268 Nov 2026

What is rising across the directory

Sources

Page checked 2026-11-05.

Badge for your README

Shows this server's rank in its category, and stars for a server that runs on your machine. It updates every hour.

MarkdownREADME.md

[![Kraken CLI MCP Server on EveryMCPServer](https://everymcpserver.com/badge/kraken-cli-mcp-server.svg)](https://everymcpserver.com/servers/kraken-cli-mcp-server)

Connect your client

Add in one click

Or add it by command or config

Settings 10

What it does

What it needs

Limits

Who it suits

Tools 56 of 152

Similar servers

CCXT MCP Server

Alpaca MCP Server

NinjaTrader MCP

NinjaTrader MCP Server

Brex MCP Server

NinjaTrader 8 MCP Server