Skip to main content
Glama
Bitpanda Developer API MCP Server

Bitpanda Developer API MCP Server

Official

Bitpanda MCP Server

CI Python 3.11+ License: Apache 2.0

IMPORTANT

This repository is archived This project is no longer maintained. Bitpanda provides an official hosted MCP server at: https://mcp.public.bitpanda.com/ For setup, authentication, and integration guides, please refer to the official documentation: https://docs.bitpanda.com/ The remainder of this README is kept for historical reference; the hosted MCP is recommended over self-hosting this implementation.

The official Model Context Protocol (MCP) server for Bitpanda. Connects AI agents — Claude, Cursor, VS Code Copilot, and any MCP-compatible client — directly to the Bitpanda API, giving them secure, read-only access to your asset portfolio, wallet balances, trade history, and real-time market prices.

Built with FastMCP 3.x, Python 3.11+, and uv.

Install the Bitpanda MCP Server

Claude Code

claude mcp add bitpanda -e BITPANDA_API_KEY=your-key -- uvx --from git+https://github.com/bitpanda-labs/bitpanda-mcp bitpanda-mcp

Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "bitpanda": {
      "command": "uvx",
      "args": ["--from", "git+https://github.com/bitpanda-labs/bitpanda-mcp", "bitpanda-mcp"],
      "env": {
        "BITPANDA_API_KEY": "your-key"
      }
    }
  }
}

Cursor / VS Code / Windsurf / any MCP client

uvx --from git+https://github.com/bitpanda-labs/bitpanda-mcp bitpanda-mcp

Set BITPANDA_API_KEY in your environment or .env file.

Get your Bitpanda API key at web.bitpanda.com/apikey.

Related MCP server: Trading 212 MCP Server

What Can You Do With Bitpanda MCP?

  • Analyze your portfolio with Claude — ask "what's my BTC allocation?" or "show me my top performing assets this month"

  • Get real-time asset prices — BTC, ETH, and hundreds of other assets via natural language

  • Review trade and transaction history — "summarize my trades from last quarter" or "show me recent transactions"

  • Build AI agents that interact with Bitpanda data — integrate Bitpanda portfolio data into any MCP-compatible AI workflow

  • Automate reporting — feed wallet balances and trade history into AI-powered analysis pipelines

Available MCP Tools

Tool

Category

Description

get_portfolio

portfolio

Aggregated portfolio view across all assets with EUR valuations and sort/sort_by

get_price

market-data

Current ticker price and currency for any asset by symbol (BTC, ETH, SOL, and more)

list_prices

market-data

Ticker prices for held assets with ticker data, or a capped market-wide list with all=true/all_assets=true and limit

get_asset

market-data

Asset metadata by asset UUID

list_wallets

wallets

All Bitpanda asset wallet balances, with non_zero, asset_id, page_size, and limit filters

list_transactions

transactions

Raw asset transaction history with wallet_id, flow, asset_id, date filters, and all=true

list_trades

trades

Normalized buy/sell activity derived from asset transactions, with operation/trade_type, asset_type, date filters, and all=true

All tools are read-only and annotated with readOnlyHint=true. The server never writes to or modifies your Bitpanda account.

MCP Prompts

Prompt

Description

portfolio_summary

Analyze portfolio composition and identify concentration risk

recent_activity

Summarize recent trades and asset transactions

Self-Hosted Bitpanda MCP Server (HTTP / Docker)

Run the server as a remote HTTP service — multiple users each authenticate per-request with their own Bitpanda API key in the X-Api-Key header. Stateless design supports horizontal scaling.

Start the HTTP server

FASTMCP_TRANSPORT=streamable-http \
FASTMCP_HOST=0.0.0.0 \
FASTMCP_PORT=8000 \
uv run bitpanda-mcp

Or with Docker (multi-stage build — runtime image contains no build tools or source code):

docker build -f ci/docker/Dockerfile -t bitpanda-mcp .
docker run -p 8000:8000 bitpanda-mcp

Connect from any MCP client

{
  "mcpServers": {
    "bitpanda": {
      "url": "http://localhost:8000/mcp",
      "headers": {
        "X-Api-Key": "YOUR_BITPANDA_API_KEY"
      }
    }
  }
}

Health check: GET /healthz → {"status": "ok"}.

Configuration & Environment Variables

Variable

Required

Default

Description

BITPANDA_API_KEY

stdio only

—

Bitpanda API key (in HTTP mode, each client sends their own key as X-Api-Key)

BITPANDA_BASE_URL

No

https://developer.bitpanda.com

Bitpanda API base URL

REQUEST_TIMEOUT_S

No

30

HTTP request timeout in seconds

FASTMCP_TRANSPORT

No

stdio

Transport: stdio or streamable-http

FASTMCP_HOST

No

127.0.0.1

HTTP bind address

FASTMCP_PORT

No

8000

HTTP port

FASTMCP_STATELESS_HTTP

No

false

Stateless mode for horizontal scaling

MCP_AUTH_HEADER

No

X-Api-Key

Header name for per-request API keys in HTTP mode. Override only if your gateway requires a different header.

Frequently Asked Questions

Do I need a Bitpanda account?
Yes — you need an active Bitpanda account and a Bitpanda API key. Generate one at web.bitpanda.com/apikey.

Is this the official Bitpanda MCP server?
Yes. This repository is maintained by Bitpanda Labs and is the official MCP integration for the Bitpanda platform.

What is the Model Context Protocol (MCP)?
MCP is an open standard that lets AI assistants connect to external data sources and tools in a structured, secure way. It's supported by Claude, Cursor, VS Code, Windsurf, and a growing ecosystem of AI development tools.

Can Claude write to my Bitpanda account or place trades?
No. All tools exposed by this server are strictly read-only. The server cannot place orders, move funds, or modify your account in any way.

Does this work with Claude.ai or ChatGPT?
It works with Claude Code (CLI) and Claude Desktop. ChatGPT and other OpenAI-based tools can connect via the remote HTTP mode if they support MCP or streamable-http. Any MCP-compatible client is supported.

Development

Requires Python 3.11+.

git clone https://github.com/bitpanda-labs/bitpanda-mcp && cd bitpanda-mcp
uv sync
cp .env.example .env  # add your Bitpanda API key

uv run pytest                  # tests (100% coverage enforced)
uv run ruff check src/ tests/  # lint
uv run ruff format src/ tests/ # format
uv build                       # build wheel + sdist

CI runs lint, tests on Python 3.11–3.14, and verifies the wheel installs cleanly.

License

Apache 2.0

Available Tools

7 tools
get_assetC
Read-only

Get asset metadata by asset UUID.

Inputs: asset_id (required). Returns: object

get_portfolioA
Read-only

Get an aggregated portfolio view with current EUR valuations.

Returns each held asset with balance, price, and EUR value. Sorted by value (default) or name. sort is a CLI-compatible alias.

Inputs: sort_by, sort. Returns: object

get_priceA
Read-only

Get the current price for an asset by its symbol (e.g. BTC, ETH).

Inputs: symbol (required). Returns: object

list_pricesA
Read-only

List ticker prices.

By default, returns held assets that have ticker data. Set all_assets/all to include the market-wide ticker list. limit caps returned rows; use limit=0 for no cap.

Inputs: all_assets, all, limit. Returns: object

list_tradesB
Read-only

List your buy/sell trades on Bitpanda.

Optional filters: trade_type/operation (buy/sell), asset_type, and date range.

Inputs: trade_type, operation, asset_type, from_including, +4 more. Returns: object

list_transactionsC
Read-only

List asset transactions with optional wallet, flow, asset, and date filters.

Inputs: wallet_id, flow, asset_id, from_including, +4 more. Returns: object

list_walletsB
Read-only

List your Bitpanda asset wallet balances.

Set non_zero=true to hide wallets with a zero balance. Use asset_id to filter by asset UUID.

Inputs: non_zero, asset_id, page_size, limit. Returns: object

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct resource or operation: asset metadata, portfolio snapshot, single price, price list, trade history, transaction history, and wallet balances. No two tools have overlapping purposes.

    Naming Consistency5/5

    Tool names follow a consistent pattern: 'get_' for retrieving a single entity (asset, portfolio, price) and 'list_' for enumerating collections (prices, trades, transactions, wallets). This makes the set predictable and easy to navigate.

    Tool Count5/5

    7 tools is well-scoped for a cryptocurrency exchange API. It covers essential read operations (asset data, portfolio, prices, trades, transactions, wallets) without unnecessary bloat, and each tool serves a clear purpose.

    Completeness4/5

    The tool surface covers the primary read-only needs: asset info, portfolio, prices, transactions, and wallets. Minor gaps exist, such as lack of order placement or deposit/withdrawal operations, but these are likely out of scope for a 'Developer API' focused on data retrieval.

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      C
      quality
      D
      maintenance
      Provides cryptocurrency market data (prices, symbols) and a gated demo trading flow via MCP tools, with safety defaults like dry-run and confirmation gates.
      6
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Exposes Trading 212 trading account, instruments, orders, history, and pies as MCP tools. Allows placing and canceling real orders (defaults to demo/paper environment).
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables fetching cryptocurrency prices, historical OHLC data, and news via CryptoCompare API through an MCP gateway.
      94 npm
      MIT