Problem or Motivation

Hi Vibe-Trading team,

Would you consider adding Trading 212 as a broker connector?

Trading 212 has an official Public API v0:

• account/cash data
• portfolio/positions
• instruments metadata
• orders
• historical account data
• pies/history endpoints

My region is Ireland, so the relevant account type is Trading 212 Invest.

Suggested staged implementation:

1. Read-only connector first:

   • trading_check
   • trading_account
   • trading_positions
   • trading_orders
   • trading_history
   • trading_quote / instrument metadata

2. Demo/paper mode support if available.

3. Live order placement only later, with explicit user approval, order-size limits, audit logging, and a kill switch.

Alternative:
If direct Trading 212 support is not planned, could Vibe-Trading support an external Trading 212 MCP server through the connector layer?

My use case:
I mainly want to use Vibe-Trading for [research/backtesting/journal analysis/read-only portfolio monitoring/paper trading/live trading].

Regards& Xiexie.

Proposed Solution

Solution 1: Adding Trading 212 to Vibe Trading. And the workflow should look like
Vibe-Trading → Trading212 connector → Trading212 API

Solution 2: Vibe-Trading support custom external broker MCP servers through the connector layer?
Vibe-Trading → generic MCP broker adapter → Trading212 MCP server → Trading212 API

If maintaining a direct connector is not practical, would it be possible for Vibe-Trading to support custom external broker MCP servers through the existing connector layer, so that a third-party MCP server for Trading 212 could map into tools like trading_account, trading_positions, trading_orders, trading_quote, and trading_history?

Area

MCP Plugin

Alternatives Considered

Alternative:
If direct Trading 212 support is not planned, could Vibe-Trading support an external Trading 212 MCP server through the connector layer?

Contribution

• I'm willing to submit a PR for this feature