Bitpanda Developer API MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SERVER_HOST | No | Host address to bind the server | 0.0.0.0 |
| SERVER_PORT | No | Port to bind the server | 8000 |
| BITPANDA_API_KEY | No | API key for local development only (not recommended for production) | |
| BITPANDA_BASE_URL | Yes | Base URL for Bitpanda Public API (e.g., https://api.bitpanda.com/v1) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_portfolioA | Get an aggregated portfolio view with current EUR valuations. Returns each held asset with balance, price, and EUR value. Sorted by
|
| get_priceA | Get the current price for an asset by its symbol (e.g. BTC, ETH). |
| list_pricesA | List ticker prices. By default, returns held assets that have ticker data. Set |
| get_assetC | Get asset metadata by asset UUID. |
| list_walletsB | List your Bitpanda asset wallet balances. Set |
| list_transactionsC | List asset transactions with optional wallet, flow, asset, and date filters. |
| list_tradesB | List your buy/sell trades on Bitpanda. Optional filters: |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| portfolio_summary | Analyze my Bitpanda portfolio and provide a summary. |
| recent_activity | Show and analyze my recent Bitpanda activity. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
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.
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.
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.
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.