Luno MCP Server

MCP Server for the Luno Cryptocurrency API. That is what the luno mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

A Model Context Protocol (MCP) server that provides access to the Luno cryptocurrency exchange API.

• Resources — Access to account balances, transaction history, and more
• Tools — Functionality for creating and managing orders, checking prices, and viewing transaction details
• Security — Secure authentication using Luno API keys
• VS Code Integration — Easy integration with VSCode, or other AI IDEs

The tools it exposes

The server publishes 14 tools. What each one is for:

• get_ticker — Market Data
• get_tickers — Market Data
• get_order_book — Market Data
• list_trades — Market Data
• get_candles — Market Data
• get_markets_info — Market Data
• get_balances — Account Information
• create_order — Trading
• cancel_order — Trading
• list_orders — Trading
• list_transactions — Transactions
• get_transaction — Transactions

What it needs from you

Configuration is passed through the environment: LUNO_API_KEY_ID, LUNO_API_SECRET, YOUR_API_KEY_ID, YOUR_API_SECRET. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Getting it running

ghcr.io/luno/luno-mcp on a container image is all you need. Most clients run it directly, so configuration is a few lines and a restart.

How it compares

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Luno's toolset — get_ticker, get_tickers, get_order_book and 11 more — is a fair guide to whether it matches your workflow. It is maintained by luno; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Luno.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.