Trading212 MCP Server

Created By
RohanAnandPandita year ago
Overview

What is Trading212 MCP Server?

The Trading212 MCP Server is an implementation of the Model Context Protocol that facilitates seamless data connectivity to the Trading212 trading platform, enabling advanced interaction capabilities for users.

How to use Trading212 MCP Server?

To use the Trading212 MCP Server, clone the repository from GitHub, configure your environment, and run the server using Docker or Python. You will need to generate an API key from your Trading212 account settings.

Key features of Trading212 MCP Server?

  • Comprehensive account management including cash balance monitoring and portfolio management.
  • Advanced order handling with support for market, limit, and stop-limit orders.
  • Real-time market data access and historical trading data.
  • Financial analysis tools for professional trading insights.
  • Full support for the MCP protocol with resource-based API endpoints.

Use cases of Trading212 MCP Server?

  1. Managing trading accounts and monitoring cash balances.
  2. Executing and managing various types of orders on the Trading212 platform.
  3. Analyzing trading data for better financial decision-making.
  4. Integrating with other tools for enhanced trading capabilities.

FAQ from Trading212 MCP Server?

  • Can I use this server for live trading?

Yes, you can use it for live trading by setting the appropriate environment in your configuration.

  • Is this an official Trading212 product?

No, this is an unofficial implementation of the Trading212 MCP protocol.

  • What are the technical requirements?

You need Python >= 3.11 and specific libraries as mentioned in the documentation.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
RohanAnandPandit
Star
0
Language
Python
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago