Connect your AI assistant — Claude, ChatGPT, Codex, Cursor, or any MCP-compatible client — directly to Bitpanda. The server is hosted remotely, so there's nothing to install locally: point your client at the HTTP endpoint and authenticate with your Bitpanda API key.How it works#
The Model Context Protocol (MCP) is an open standard that lets AI assistants securely connect to external services. The Bitpanda MCP server exposes your account and market data as tools your agent can call in plain language, authenticating each request with the x-api-key header you supply. Create a key in your Bitpanda Account Settings and assign the scopes the tools you intend to use require.Capping how much your agent can trade#
Giving an agent an API key with the Trade (Write) scope means it can execute trades on your behalf, so it’s worth putting server-side limits in place before handing over the key.The Public API MCP server exposes Bitpanda’s trading limits as two tools: one to check the current limits and remaining budget, and one to configure them. You can set separate daily buy and sell volume limits for the API key, denominated in a currency of your choice, such as EUR.For example, you can ask your assistant:Get the current trading limits for my Bitpanda API key.
Set my daily trading limits to 100 EUR for buys and 100 EUR for sells.
Buy and sell limits are tracked separately. A limit of 100 EUR for buys and 100 EUR for sells therefore allows up to 100 EUR of buying volume and 100 EUR of selling volume per day — it is not a single 100 EUR limit shared across both sides.If no trading limit has been configured yet, the check tool may return trading_limit.not_configured. That is expected for a key without limits and does not mean the key is broken.When setting limits, the tool requires three values:the currency the limits are denominated in
Because setting trading limits is irreversible for that API key, your assistant should make the intended buy limit, sell limit, and currency clear before executing the change rather than guessing ambiguous values.Limits are enforced server-side#
Trading limits are enforced by Bitpanda for the API key itself, not by the agent. That means the restriction still applies even if the agent behaves unexpectedly, receives a malicious prompt, or is instructed to ignore its own safeguards.A few important things to know:Limits are permanent for that API key. Once configured, they cannot be changed or removed. To use different limits, create a new API key.
Budgets reset daily. The remaining buy and sell budget is returned whenever you check the current limits.
Buy and sell budgets are independent. Activity on one side does not consume the other side’s daily allowance.
Setting a trading limit is optional, but recommended for any API key you give to an agent. It limits the amount of trading the key can initiate each day and provides a server-side guardrail against bugs, unexpected agent behavior, and prompt injection without relying on the agent to enforce its own limits.Choose your server#
Two remote servers are available over HTTP transport — pick whichever API you're connecting to:| Server | Endpoint |
|---|
| Public API | https://mcp.public.bitpanda.com |
| Fusion | https://mcp.fusion.bitpanda.com |
Use different server names. Give each server a distinct name (bitpanda vs. bitpanda-fusion) when registering it with your client. If you add both with the same name, the second one overwrites the first — you won't be able to use them side by side.
In every command and config snippet below, YOUR_BITPANDA_API_KEY is a placeholder — replace it with a key generated in your own Bitpanda Account Settings, not a shared or example key.Public API MCP Server (bitpanda)#
Fusion MCP Server (bitpanda-fusion)#
You can register both servers at once (bitpanda and bitpanda-fusion) if you need tools from both APIs in the same client. Trading and earn tools require the matching scopes on your API key. If tools don't appear after connecting, restart the app.