Trading 212 MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TRADING212_API_KEY | Yes | Your Trading 212 API key | |
| TRADING212_ENVIRONMENT | No | Environment (demo or live), defaults to demo | demo |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_account_infoB | Retrieve account metadata including currency code and account ID |
| get_account_cashB | Get detailed cash balance information including free, invested, blocked, and total amounts |
| get_account_summaryB | Get comprehensive account summary with cash, invested amounts, profit/loss, and available funds |
| get_portfolioA | List all open positions in the portfolio with current prices, quantities, and profit/loss |
| get_positionC | Get detailed information about a specific position by ticker symbol |
| get_ordersB | Retrieve all active orders (pending, processing, etc.) |
| get_orderB | Get detailed information about a specific order by order ID |
| cancel_orderC | Cancel an active order by order ID |
| place_market_orderC | Place a market order to buy or sell at the current market price |
| place_limit_orderC | Place a limit order to buy or sell at a specified price or better |
| place_stop_orderC | Place a stop order that becomes a market order when the stop price is reached |
| place_stop_limit_orderB | Place a stop-limit order that becomes a limit order when the stop price is reached |
| get_instrumentsB | List all tradeable instruments with metadata including ISIN, currency, type, and trading schedules |
| get_exchangesB | Get information about exchanges and their trading schedules |
| get_piesA | List all investment pies (portfolio buckets) with their configurations and holdings |
| get_pieC | Get detailed information about a specific pie by ID |
| create_pieC | Create a new investment pie with specified instruments and allocations |
| update_pieC | Update an existing pie configuration |
| delete_pieC | Delete an investment pie by ID |
| get_order_historyC | Get historical orders with pagination support |
| get_dividendsC | Get dividend payment history with pagination support |
| get_transactionsB | Get transaction history including deposits, withdrawals, orders, dividends, and fees |
| request_exportC | Request a CSV export of account data for a specified time period |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 23 tools
Each tool has a clearly distinct purpose targeting specific resources and actions, such as cancel_order vs. get_order for order management, and get_portfolio vs. get_position for portfolio details. No tools appear to overlap or cause confusion, with clear boundaries between operations like place_limit_order and place_stop_limit_order.
All tool names follow a consistent verb_noun pattern using snake_case, such as get_account_info, place_market_order, and update_pie. There are no deviations in naming conventions, making the set predictable and easy to navigate for an agent.
With 23 tools, the count is slightly high but reasonable for a comprehensive trading platform covering orders, pies, account info, and instruments. It feels slightly heavy but not excessive, as each tool serves a distinct function in the domain.
The tool set provides complete CRUD/lifecycle coverage for trading and portfolio management, including order placement, cancellation, pie management, account data retrieval, and transaction history. No obvious gaps exist; agents can perform all core workflows without dead ends.