TradePilot 212

简体中文 · English

TradePilot 212 is a self-hosted MCP application for Trading 212 Invest. It connects a personal Trading 212 account to ChatGPT, provides a compact portfolio and trade-plan UI, and keeps every broker write behind an explicit confirmation step.

Each deployment belongs to one user. Your Trading 212 credentials stay in your own environment; the repository owner does not run a shared brokerage backend.

Design goals

• ChatGPT-first workflow — use symbols, company names, amounts, percentages, or exact quantities in normal conversation.

• Explicit execution boundary — analysis and order preparation are read-only; a broker write happens only after confirmation in the app UI.

• Self-hosted by default — Cloudflare Workers is the recommended hosted path; Node.js and Docker/VPS are also supported.

• Small runtime surface — the Worker handles account access, instrument resolution, validation, state, and execution. Research and scheduling stay outside the broker bridge.

• Recoverable failures — ambiguous write outcomes are never retried automatically and can be checked against current broker state.

• Portable UI — responsive inline/fullscreen layouts, an in-flow order workspace that does not depend on fixed iframe overlays, English and Simplified Chinese, with an extensible locale registry.

Related MCP server: Trading 212 MCP Server

What is included

• Trading 212 Invest account summary, positions, pending orders, and recent TradePilot activity

• separate Demo and Live credentials and UI states

• short / medium / long trade-plan cards

• expandable thesis, catalysts, risks, counter-case, sources, and data timestamps

• ticker, symbol, company-name, and partial-name resolution

• order sizing by:

  • exact quantity

  • target monetary amount

  • percentage of available cash for buys

  • percentage of the total held position for sells

  • all currently tradable shares for sells

• Market, Limit, Stop, and Stop-Limit order drafts

• transparent intent-to-quantity conversion with manual-edit indication

• reference-price freshness notices

• structured errors rendered in the selected UI language

• one-time confirmation state and no automatic write retries

• read-back verification after an uncertain order/cancellation response

• OAuth + PKCE for the MCP connection

• Cloudflare Durable Objects or local file-backed state through the same StateStore contract

Requirements

• Node.js 22+

• pnpm 11+

• a Trading 212 Invest account with Public API access

• a Cloudflare account for the recommended hosted deployment

• a ChatGPT plan/client that supports custom Apps / MCP connections

Install pnpm if needed:

npm install -g pnpm@11

Setup

1. Clone and install

git clone https://github.com/Kukutx/TradePilot212.git
cd TradePilot212
pnpm install

2. Create local configuration

pnpm setup

pnpm setup creates .env.local if it does not already exist and generates strong local values for the OAuth login password and signing secret.

Open .env.local and add the Trading 212 environments you intend to use:

T212_DEMO_API_KEY=
T212_DEMO_API_SECRET=

T212_LIVE_API_KEY=
T212_LIVE_API_SECRET=

Demo and Live use separate Trading 212 credentials. Configure either one or both.

Trading 212 API documentation:

• https://helpcentre.trading212.com/hc/en-us/articles/14584770928157-Trading-212-API-key

• https://docs.trading212.com/

For portfolio-only use, read permissions are sufficient. Order review/execution requires the corresponding order permissions on the Trading 212 API key.

3. Check the configuration

pnpm doctor

This checks the runtime, local OAuth configuration, and Trading 212 connectivity with read-only requests. It does not place an order.

4. Deploy a personal Worker

pnpm deploy

The deployment command:

1. validates the local configuration and project,

2. opens Cloudflare authentication when required,

3. synchronizes the instance settings through Worker Secrets,

4. builds the app,

5. deploys the Worker,

6. prints the App and MCP endpoints.

Typical output:

App: https://tradepilot212.<your-subdomain>.workers.dev
MCP: https://tradepilot212.<your-subdomain>.workers.dev/mcp

Check the deployment without publishing it:

pnpm deploy -- --dry-run

Use a different Worker name:

pnpm deploy -- --name=my-tradepilot

5. Connect ChatGPT

In ChatGPT, open the Apps settings and create a custom MCP connection. Use the /mcp URL printed by the deployment command.

The OAuth page asks for the APP_LOGIN_PASSWORD stored in your own .env.local. Do not paste Trading 212 API credentials into ChatGPT.

After the connection is established, normal prompts can be simple:

Show my Trading 212 Live portfolio.
Analyze Nvidia in the context of my current positions.
Compare AMD, Nvidia, and Broadcom for a one-month horizon.
Prepare a Demo order for 0.2 shares of NVDA.
Use about €100 to buy Nvidia in Live.
Sell half of my Apple position.
Sell all currently tradable Apple shares.
Prepare a 220 USD limit buy for 0.5 NVDA. Do not submit it.

TradePilot resolves and normalizes the request into an editable quantity-based order. The broker write still requires the final confirmation in the UI.

Order flow

User request
  ↓
Instrument resolution + account/position read
  ↓
Sizing and editable order draft
  ↓
Server validation + data freshness notices
  ↓
Short-lived one-time confirmation
  ↓
Explicit user confirmation
  ↓
Trading 212 write

If a write times out or returns an ambiguous server error, TradePilot does not resend it. The UI offers a read-only status check that looks for a matching pending order or a corresponding position change. An inconclusive result remains inconclusive; it is never converted into an automatic retry.

See docs/ORDERING.md for the sizing rules and edge cases.

Scheduling and market research

TradePilot intentionally does not contain a stock-research scheduler, news crawler, or autonomous trading loop.

A scheduled ChatGPT task can perform market research, read the portfolio through TradePilot, and render a trade plan. Execution remains a separate interactive action.

See docs/AUTOMATION.md.

Configuration

Common instance settings:

DEFAULT_TRADING_ENV=demo
MAX_ORDER_NOTIONAL=5000
MAX_ORDER_QUANTITY=100000
CONFIRMATION_TTL_SECONDS=90

DEFAULT_TRADING_ENV applies only when a request does not explicitly select Demo or Live.

Set MAX_ORDER_NOTIONAL=0 or MAX_ORDER_QUANTITY=0 to disable the corresponding TradePilot application-level cap. Trading 212 account/instrument rules and explicit confirmation still apply.

Local development

Node development server:

pnpm setup
# fill .env.local
pnpm doctor
pnpm dev

Local MCP endpoint:

http://localhost:8000/mcp

For temporary ChatGPT testing from a local Node process:

pnpm dev:chatgpt

This uses a Cloudflare Quick Tunnel. The URL is temporary; use a normal Worker deployment for a stable personal endpoint.

Local Cloudflare runtime:

cp .dev.vars.example .dev.vars
# fill .dev.vars
pnpm dev:cloudflare

Validation

pnpm check
pnpm smoke
pnpm audit --prod
pnpm release:check
pnpm deploy -- --dry-run

The repository CI runs type checking, tests, production builds, dependency audit, release-safety checks, and a Wrangler deployment dry run.

Architecture

ChatGPT / MCP host
        │
        ▼
  Hono + OAuth/PKCE
        │
        ▼
 TradingService ───── Trading212Client
        │                   │
        │                   ▼
        │              Trading 212
        ▼
    StateStore
     ├─ file-backed state (Node)
     └─ Durable Object / SQLite (Workers)

React App UI ← MCP App resource

The core does not depend on the Node filesystem or Cloudflare APIs. Runtime-specific concerns live under src/adapters/.

More detail: docs/ARCHITECTURE.md.

Self-hosting model

User A → User A's ChatGPT → User A's Worker → User A's Trading 212 credentials
User B → User B's ChatGPT → User B's Worker → User B's Trading 212 credentials

Do not publish a personal deployed Worker as a shared endpoint for unrelated users. A multi-user hosted service requires separate identity, credential isolation, and authorization architecture that this repository intentionally does not implement.

See docs/PUBLISHING.md.

Security notes

• .env.local, .dev.vars, .data, build output, and Wrangler state are excluded from Git.

• Trading 212 API credentials are deployed as Worker Secrets, not source configuration.

• Demo and Live credentials are separate.

• order and cancellation confirmations are short-lived and one-time.

• write requests are never automatically retried after an ambiguous response.

• order constraints are revalidated immediately before submission.

• recent activity stores order metadata only; it does not store API credentials.

Run pnpm release:check before publishing changes.

See SECURITY.md.

Project layout

src/
├─ adapters/
│  ├─ cloudflare/       Workers + Durable Objects + Static Assets
│  └─ node/             Node server + file-backed state
├─ app/                 shared HTTP/MCP application
├─ core/                OAuth, MCP tools, broker client, trading rules, state
├─ shared/              runtime-neutral contracts and metadata
└─ ui/                  React MCP App UI and locale dictionaries

scripts/                 setup, diagnostics, deployment, smoke checks
docs/                    architecture, ordering, automation, publishing, i18n
.github/workflows/        CI

License

MIT. See LICENSE.

Disclaimer

TradePilot 212 is a software integration project, not investment advice. Review market information and every order yourself. Trading 212 controls API availability, permissions, instruments, and broker-side limits, and those may change independently of this repository.