MCP Bitpanda Server
The MCP Bitpanda Server provides programmatic access to Bitpanda API features, enabling you to:
Retrieve detailed asset information by symbol (e.g., BTC, XAU)
Fetch OHLC (Open/High/Low/Close) data for assets by symbol, fiat currency, and timeframe (day/week)
List user's trades with filtering by type (buy/sell) and cursor-based pagination
View asset wallets grouped by asset type
Access fiat wallets and their transactions with filtering by type (buy, sell, deposit, withdrawal, transfer, refund) and status (pending, processing, finished, canceled)
List crypto wallets and transactions with filtering by type (buy, sell, deposit, withdrawal, transfer, refund, ico) and status (pending, processing, unconfirmed_transaction_out, open_invitation, finished, canceled)
Get commodity transactions with pagination support
Used as the runtime environment for the MCP server, allowing it to execute JavaScript code.
Used for package management and running scripts for the MCP server.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@MCP Bitpanda Server show me my recent Bitcoin trades"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP Bitpanda Server
A Model Context Protocol (MCP) server that exposes tools for interacting with the Bitpanda API. This server allows programmatic access to Bitpanda features like trades, wallets, and transactions via the MCP protocol.
Prerequisites
Node.js (v18 or later recommended)
npm (comes with Node.js)
A Bitpanda API Key (set as
BITPANDA_API_KEYenvironment variable)(Optional) MCP-compatible client or runner (e.g., VSCode extension, CLI)
Related MCP server: FireHydrant MCP Server
Setup
Clone the repository or ensure you are in the project directory.
Install dependencies:
npm installBuild the server:
npm run buildThis will create a
builddirectory with the compiled JavaScript code.
Installing via Smithery
To install MCP Bitpanda Server for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @matteoantoci/mcp-bitpanda --client claudeRunning the Server
Directly:
node build/index.jsor, if you have a start script:
npm run startVia MCP runner: Configure your MCP client to run the server using stdio transport. Example MCP settings entry:
"mcp-bitpanda": { "transportType": "stdio", "command": "node", "args": [ "/path/to/mcp-bitpanda/build/index.js" ] // Add environment variables, e.g., for the API key "environmentVariables": { "BITPANDA_API_KEY": "YOUR_BITPANDA_API_KEY" // Replace with your actual API key or use a secure method to provide it } // ... other optional settings ... }
Available Tools
get_asset_info: Retrieves detailed information for a specific asset by its symbol (e.g., BTC, XAU).Parameters:
symbol(string, required)Note: This tool does not require an API key.
get_ohlc: Retrieves OHLC (Open/High/Low/Close) data for a specific asset, fiat currency, and timeframe.Parameters:
symbol(string, required): The trading symbol.fiatCurrency(string, required): The fiat currency (e.g., USD, EUR).timeframe(string, required): Either "day" or "week".
Note: This tool does not require an API key.
list_trades: Lists all user's trades from the Bitpanda API. Newest trades come first. Response is cursor paginated.Parameters:
type(string, optional): One ofbuyorsell.cursor(string, optional): Id of the last known trade by the client. Only trades after this id are returned. Empty or missing cursor parameter will return trades from the start.page_size(integer, optional): Size of a page for the paginated response.
list_asset_wallets: Lists all user's asset wallets grouped by asset type from the Bitpanda API.Parameters: None.
list_fiat_wallets: Lists all user's fiat wallets from the Bitpanda API.Parameters: None.
list_fiat_transactions: Lists all user's fiat transactions from the Bitpanda API. Newest fiat transactions come first. Response is cursor paginated.Parameters:
type(string, optional): buy, sell, deposit, withdrawal, transfer, refund.status(string, optional): pending, processing, finished, canceled.cursor(string, optional): Id of the last known fiat transaction by the client. Only fiat transactions after this id are returned. Empty or missing cursor parameter will return fiat transactions from the start.page_size(integer, optional): Size of a page for the paginated response.
list_crypto_wallets: Lists all user's crypto wallets from the Bitpanda API.Parameters: None.
list_crypto_transactions: Lists all user's crypto transactions from the Bitpanda API. Newest crypto transactions come first. Response is cursor paginated.Parameters:
type(string, optional): One ofbuy,sell,deposit,withdrawal,transfer,refundorico.status(string, optional): One ofpending,processing,unconfirmed_transaction_out,open_invitation,finishedorcanceled.cursor(string, optional): Id of the last known crypto transaction by the client. Only crypto transactions after this id are returned. Empty or missing cursor parameter will return crypto transactions from the start.page_size(integer, optional): Size of a page for the paginated response.
list_commodity_transactions: Lists all user's commodity transactions from the Bitpanda API. Newest commodity transactions come first. Response is cursor paginated.Parameters:
cursor(string, optional): Id of the last known commodity transaction by the client. Only commodity transactions after this id are returned. Empty or missing cursor parameter will return commodity transactions from the start.page_size(integer, optional): Size of a page for the paginated response.
Extending
To add more Bitpanda API endpoints as tools, implement a new tool file in src/tools/ and register it in src/tools/index.ts.
Available Tools
8 toolsget_asset_infoC
Retrieves detailed information for a specific asset by its symbol.
Inputs: symbol (required).
list_asset_walletsB
Lists all user's asset wallets grouped by asset type from the Bitpanda API.
Inputs: no named parameters.
list_commodity_transactionsA
Lists all user's commodity transactions from the Bitpanda API. Newest commodity transactions come first. Response is cursor paginated.
Inputs: cursor, page_size.
list_crypto_transactionsA
Lists all user's crypto transactions from the Bitpanda API. Newest crypto transactions come first. Response is cursor paginated.
Inputs: type, status, cursor, page_size.
list_crypto_walletsB
Lists all user's crypto wallets from the Bitpanda API.
Inputs: no named parameters.
list_fiat_transactionsA
Lists all user's fiat transactions from the Bitpanda API. Newest fiat transactions come first. Response is cursor paginated.
Inputs: type, status, cursor, page_size.
list_fiat_walletsB
Lists all user's fiat wallets from the Bitpanda API.
Inputs: no named parameters.
list_tradesA
Lists all user's trades from the Bitpanda API. Newest trades come first. Response is cursor paginated.
Inputs: type, cursor, page_size.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 8 tools
The tools are mostly distinct, focusing on different resource types like assets, wallets, transactions, and trades. However, there is some potential overlap between 'list_trades' and the transaction tools (commodity, crypto, fiat), as trades might be a subset or related to transactions, which could cause minor confusion without additional context.
All tool names follow a consistent verb_noun pattern with 'get_' or 'list_' prefixes, using snake_case throughout. This predictability makes it easy for agents to understand and select tools based on their naming conventions.
With 8 tools, the server is well-scoped for a Bitpanda API integration, covering key areas like asset information, wallets, transactions, and trades. Each tool serves a clear purpose without being overly broad or too limited for the domain.
The tools provide good read/list coverage for assets, wallets, transactions, and trades, but there are notable gaps in CRUD operations. For example, there are no tools for creating, updating, or deleting resources (e.g., executing trades or modifying wallets), which limits the server's functionality to querying only.
Related MCP Connectors
Trade and invest in tokenized stocks: prices, holdings, P&L, unsigned market/limit/recurring trades.
Unified financial infrastructure connecting AI agents directly to trade live/demo brokerage accounts, Web3 non-custodial wallets, real-time market data across equities, ETFs, crypto, forex, options, DeFi swaps, and prediction markets, institutional research feeds, and algorithmic strategy backtesters.
Keyless prediction-market data across 12 venues plus paper-trading of crypto spot, futures, and PM.
Agentic brokerage access to a US brokerage account: quotes, orders, positions, cash and documents.
Related MCP Servers
- AlicenseBqualityDmaintenanceEnables interaction with Linear's API for managing issues, teams, and projects programmatically through the Model Context Protocol.783 npm4MIT
- AlicenseNot gradedqualityDmaintenanceEnables interaction with FireHydrant's incident management API through the Model Context Protocol. Provides programmatic access to FireHydrant's features for managing incidents, retrospectives, and operational workflows.385 npm5MIT
- FlicenseNot gradedqualityAmaintenanceEnables programmatic access to Tiingo financial data—stock prices, news, forex, fundamentals, and corporate actions—through the Model Context Protocol.-
- FlicenseNot gradedqualityAmaintenanceEnables interaction with Interactive Brokers through the official Web API via the Model Context Protocol, allowing clients to access brokerage account management, reporting, and trading endpoints.-