trading212-mcp

MCP server for the Trading 212 public API — equities and ETF investing on Invest and Stocks ISA accounts. It exposes the account, portfolio, order, pie, and history endpoints as MCP tools, defaults to the demo (paper trading) environment, and keeps trading tools hidden unless explicitly enabled.

Features

• Read coverage of the whole public API: account summary, instrument universe, exchange schedules, open positions, pending orders, pies, historical orders, dividends, cash transactions, and CSV exports.

• Trading tools (order placement/cancellation, pie management, export requests) are opt-in via an environment flag and stay invisible to the MCP client otherwise.

• Demo environment by default; live is an explicit choice.

• Responses are trimmed to the fields a trader acts on, and list tools accept a limit parameter to keep payloads small.

• One automatic retry on HTTP 429, honouring the Retry-After header capped at 30 seconds (Trading 212 rate limits are strict and per-endpoint).

• stdio transport by default, HTTP (/mcp) on request.

Related MCP server: tastytrade-mcp

Tools

Read tools (always registered):

Write tools (registered only when T212_MCP_ENABLE_TRADING is truthy):

Configuration

All configuration is via environment variables — never commit credentials.

Getting started

Run straight from the repository with uv:

uvx --from git+https://github.com/florinel-chis/trading212-mcp trading212-mcp

The server speaks stdio by default; add --transport http --port 8000 to serve MCP over HTTP at /mcp instead. HTTP binds 127.0.0.1 by default, and a non-loopback --host is refused unless --allow-remote is also passed — read the Safety section before using that flag.

MCP client configuration

Add the server to your MCP client's configuration (stdio, via uvx):

{
  "mcpServers": {
    "trading212": {
      "command": "uvx",
      "args": ["--from", "git+https://github.com/florinel-chis/trading212-mcp", "trading212-mcp"],
      "env": {
        "T212_API_KEY": "your-api-key",
        "T212_API_SECRET": "your-api-secret"
      }
    }
  }
}

Or run the Docker image (build it first, see below):

{
  "mcpServers": {
    "trading212": {
      "command": "docker",
      "args": [
        "run", "-i", "--rm",
        "-e", "T212_API_KEY",
        "-e", "T212_API_SECRET",
        "trading212-mcp"
      ],
      "env": {
        "T212_API_KEY": "your-api-key",
        "T212_API_SECRET": "your-api-secret"
      }
    }
  }
}

Docker

docker build -t trading212-mcp .

# stdio (what MCP clients spawn)
docker run -i --rm -e T212_API_KEY -e T212_API_SECRET trading212-mcp

# HTTP at http://127.0.0.1:8000/mcp — publish the port on loopback only:
# the MCP endpoint is unauthenticated (see Safety)
docker run --rm -p 127.0.0.1:8000:8000 -e T212_API_KEY -e T212_API_SECRET \
  trading212-mcp --transport http --host 0.0.0.0 --port 8000 --allow-remote

(--host 0.0.0.0 binds inside the container so the port mapping works — which is why --allow-remote is needed; the 127.0.0.1: prefix on -p keeps the endpoint reachable from this machine only.)

Safety

• The HTTP transport has no authentication: anyone who can reach the /mcp endpoint can call every registered tool — read the account, and place/cancel orders or delete pies if T212_MCP_ENABLE_TRADING is set — all signed with your API key. Keep it bound to 127.0.0.1 (the CLI default; with Docker, publish as -p 127.0.0.1:8000:8000) or put it behind an authenticating reverse proxy. Never expose it directly on a public or shared network.

• The server defaults to the demo (paper trading) environment; set T212_ENV=live deliberately.

• Trading tools are not registered — invisible to the MCP client — unless T212_MCP_ENABLE_TRADING is truthy.

• The Trading 212 API is v0 beta: order endpoints are not idempotent (resending a request may create duplicate orders), and rate limits are strict and per-endpoint (each tool documents its limit).

• Use at your own risk. Nothing here is investment advice.

Development

uv sync
uv run pytest -q
uv run ruff check .

License

MIT