Trading 212 MCP Server

Trading 212 MCP Server

An MCP (Model Context Protocol) server for the Trading 212 Public API, packaged as a Docker container with an SSE transport for hosting on Obot (or any MCP host that speaks SSE).

It exposes the account, instruments, orders, history and pies endpoints as MCP tools.

⚠️ This server can place and cancel real orders. It targets the demo / paper environment by default. Only set TRADING212_LIVE=true once you understand the risk.

Environments

Trading 212 runs two fully separate environments, each with its own credentials:

| TRADING212_LIVE | Base URL | Money | |---|---|---| | _unset / false_ (default) | https://demo.trading212.com/api/v0 | Paper | | true | https://live.trading212.com/api/v0 | Real |

Authentication

The Public API uses HTTP Basic auth — Base64("API_KEY:API_SECRET"). Generate the key and secret in the Trading 212 app under Settings > API; the secret is shown only once.

Configuration

Provide config one of two ways (env vars are the simplest):

Environment variables

| Variable | Required | Description | |---|---|---| | TRADING212_API_KEY | yes | API key from the Trading 212 app | | TRADING212_API_SECRET | yes | API secret (shown once at generation) | | TRADING212_LIVE | no | true for the live/real-money environment; default uses demo/paper | | SERVER_HOST | no | Bind host (default 0.0.0.0) | | SERVER_PORT | no | Bind port (default 8000) |

Config file (Docker volume)

Mount a JSON file at /config/config.json (takes priority over env vars):

{
  "api_key": "your-api-key-here",
  "api_secret": "your-api-secret-here",
  "live": false
}

Running

docker-compose

cp .env.example .env   # then edit values
docker compose up --build

docker

docker build -t trading212-mcp .
docker run -p 8000:8000 \
  -e TRADING212_API_KEY=... \
  -e TRADING212_API_SECRET=... \
  -e TRADING212_LIVE=false \
  trading212-mcp

The server then exposes:

• GET /sse — MCP SSE connection endpoint (point your MCP host here)
• POST /messages/ — MCP message endpoint (used internally by the SSE transport)
• GET /health — liveness check (reports the active environment)

Deploying to Obot

1. Build & push the image (the included GitHub Actions workflow publishes

ghcr.io/nigelvanhattum/trading212-mcp:latest on push to main).

1. The Obot catalog entry lives in the obot-mcp-repository repo as trading212.yaml.
2. In Obot, add the server and set TRADING212_API_KEY, TRADING212_API_SECRET, and

optionally TRADING212_LIVE.

Tools

| Module | Tools | |---|---| | account | get_account_summary, get_positions | | instruments | list_instruments, list_exchanges | | orders | list_orders, get_order, cancel_order, place_market_order, place_limit_order, place_stop_order, place_stop_limit_order | | history | get_historical_orders, get_dividends, get_transactions, list_exports, request_export |

Order convention: a positive quantity buys, a negative quantity sells (e.g. -10.5). Orders execute only in the account's main currency.

Development

pip install -e ".[dev]"
pytest

The Docker build runs the test suite as a build stage — a failing test fails the image build.

API reference

• Key concepts: https://docs.trading212.com/api/section/general-information/key-concepts
• Environments: https://docs.trading212.com/api/section/general-information/api-environments
• Full API: https://docs.trading212.com/api