MCP Bitpanda Server

You can programmatically access Bitpanda features through an MCP server that exposes a range of tools for trades, wallets, and transactions. This enables you to integrate Bitpanda data and actions into your applications or automation workflows using the MCP protocol.

How to use

To use this MCP server with an MCP client, connect your client to the local or remote stdio-based server configuration. Start the server, then issue tool calls that map to Bitpanda API endpoints such as retrieving asset information, OHLC data, or listing trades and wallets. Your client will receive structured responses you can feed into dashboards, alerting, or automated trading/portfolio workflows. Ensure you provide the required environment variable BITPANDA_API_KEY so the server can authenticate with Bitpanda when making API requests.

How to install

Prerequisites: Node.js 18 or later, npm comes with Node.js, a Bitpanda API Key set as BITPANDA_API_KEY in your environment, and optionally an MCP-compatible client or runner.

1. Clone the project directory or navigate to the project folder.

npm install

npm run build

Build creates a build directory with the compiled JavaScript code you will run to start the server.

Optional integration via Smithery provides an automatic client install for Claude Desktop.

npx -y @smithery/cli install @matteoantoci/mcp-bitpanda --client claude

Run the server directly or via an MCP runner

Directly run the server from the built output. You can start it with either of these commands.

node build/index.js

npm run start

Configure the MCP runner (stdio)

If you are using an MCP runner with stdio transport, configure your MCP client to start the server with the following settings. Replace the path with the actual location of your built index file and provide your API key in a secure manner.

"mcp-bitpanda": {
  "transportType": "stdio",
  "command": "node",
  "args": [
    "/path/to/mcp-bitpanda/build/index.js"
  ],
  "environmentVariables": {
    "BITPANDA_API_KEY": "YOUR_BITPANDA_API_KEY"
  }
}

Available tools

get_asset_info

Retrieves detailed information for a specific asset by its symbol (e.g., BTC, XAU). This tool does not require an API key.

get_ohlc

Retrieves OHLC data for a specific asset, fiat currency, and timeframe. Requires symbol, fiatCurrency, and timeframe (day or week). Not requiring an API key.

list_trades

Lists all user trades from the Bitpanda API. Newest trades come first. Response is cursor paginated. Parameters: type, cursor, page_size.

list_asset_wallets

Lists all user asset wallets grouped by asset type. No parameters.

list_fiat_wallets

Lists all user fiat wallets. No parameters.

list_fiat_transactions

Lists all user fiat transactions. Newest fiat transactions come first. Cursor-paginated. Parameters: type, status, cursor, page_size.

list_crypto_wallets

Lists all user crypto wallets. No parameters.

list_crypto_transactions

Lists all user crypto transactions. Newest crypto transactions come first. Cursor-paginated. Parameters: type, status, cursor, page_size.

list_commodity_transactions

Lists all user commodity transactions. Newest first. Cursor-paginated. Parameters: cursor, page_size.