MCP server for Trading 212 API - portfolio, orders, pies, dividends, and analytics
If you already use Trading212, the trading212 mcp server is the piece that lets your assistant work with it directly. MCP server for Trading 212 API - portfolio, orders, pies, dividends, and analytics.
Connect your AI assistant to your Trading 212 brokerage account. Ask questions about your portfolio, place trades, manage pies, and analyze dividends - all through natural language.
The server ships on PyPI as trading212-mcp-server, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Account — The Account tool exposed by this serverTrading — The Trading tool exposed by this serverPies — The Pies tool exposed by this serverHistory — The History tool exposed by this serverConfiguration is passed through the environment: TRADING212_API_KEY, TRADING212_API_SECRET, ENVIRONMENT. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
This sits in the database access group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Trading212's toolset — Account, Trading, Pies and 1 more — is a fair guide to whether it matches your workflow. It is maintained by KyuRish; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Trading212's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Account | The Account tool exposed by this server. |
| Trading | The Trading tool exposed by this server. |
| Pies | The Pies tool exposed by this server. |
| History | The History tool exposed by this server. |
{
"mcpServers": {
"trading212": {
"command": "uvx",
"args": ["trading212-mcp-server"],
"env": {
"TRADING212_API_KEY": "<your-api-key>",
"TRADING212_API_SECRET": "<your-api-secret>",
"ENVIRONMENT": "live"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| TRADING212_API_KEY | Credential the server authenticates with. | Yes |
| TRADING212_API_SECRET | Credential the server authenticates with. | Yes |
| ENVIRONMENT | Configuration value read at startup. | Optional |
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.