Trading 212 Controlled MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TRADING212_API_KEY | Yes | Your Trading 212 API key used for authentication. | |
| TRADING212_API_SECRET | Yes | Your Trading 212 API secret used for authentication. | |
| TRADING212_ENVIRONMENT | No | The environment to use: 'demo' (default) or 'live'. | 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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_account_summaryB | Retrieve the current account summary. Read-only. |
| get_cashA | Retrieve account summary for cash information only. Read-only; no transfers or withdrawals. |
| get_positionsA | List open positions, optionally for one exact Trading 212 ticker. Read-only. |
| get_portfolioA | Build a current portfolio view with market values and allocation from open positions. Read-only. |
| get_pending_ordersA | List currently pending orders. Read-only. |
| get_historical_ordersA | List completed/cancelled historical orders with cursor pagination. Read-only. |
| get_transactionsA | List account cash movements with cursor pagination, optionally from an ISO-8601 time. Read-only. |
| get_dividendsA | List paid dividends with cursor pagination and optional ticker filter. Read-only. |
| preview_market_orderA | Create a five-minute preview for a real buy or sell Market order. It does not place an order. Present every detail and wait for the user to directly confirm before calling execute_confirmed_action. |
| preview_order_cancellationA | Check a pending order and create a five-minute cancellation preview. It does not cancel anything. Present the order details and wait for direct user confirmation before calling execute_confirmed_action. |
| execute_confirmed_actionA | Execute exactly one previously previewed market order or pending-order cancellation. Call only after the user directly confirms the exact preview. The confirmation token is single-use and expires after five minutes; executions are never retried automatically. |
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 11 tools
Most tools are clearly distinct, but there is overlap between get_cash and get_account_summary, and between get_positions and get_portfolio since both concern position/account data. The descriptions help clarify intent, but an agent could still select the wrong getter without deeper inspection.
All tools follow a consistent get_/preview_/execute_ prefix pattern with clear object/action naming. There is no mixing of casing, verb styles, or vague generic names.
11 tools is well within the ideal range for a trading account server. Each tool serves a distinct read or controlled-action role, and there is no obvious bloat or unnecessary duplication.
The read surface is thorough, covering cash, positions, portfolio, orders, transactions, dividends, and account summary. The action surface supports market order previews, cancellation previews, and confirmed execution; missing limit/stop order types and order modification are minor given the apparent controlled scope.