Gainium MCP Server

Connect Gainium to Claude, Cursor or any other MCP client and it stops being a tab you switch to. MCP server for Gainium — manage trading bots, deals, and balances via AI assistants. The gainium mcp server is what makes that connection.

What the server does

An MCP (Model Context Protocol) server for Gainium — the crypto trading bot platform. Lets AI assistants manage your bots, deals, balances, and more through a standard MCP interface.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• Read — only key**: read tools only (list_, get_, discover, backtest_info, get_screener, list_presets)
• Bots — The Bots tool exposed by this server
• Deals — The Deals tool exposed by this server
• Backtest — The Backtest tool exposed by this server

Installation

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

Credentials and setup notes

Configuration is passed through the environment: GAINIUM_API_KEY, GAINIUM_API_SECRET, GAINIUM_MCP_TRANSPORT, GAINIUM_OAUTH_ISSUER, MCP_INTROSPECTION_SECRET, GAINIUM_MCP_PUBLIC_URL, GAINIUM_INTROSPECTION_URL, GAINIUM_MCP_HOST. 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.

Where it fits

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Gainium's toolset — Read, Bots, Deals and 1 more — is a fair guide to whether it matches your workflow. It is maintained by io.gainium; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Worth knowing first

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• 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.