TradingView Chrome MCP — Standalone Windows .exe

Let your AI assistant remote-control your TradingView tab in Chrome — with a single portable Windows executable.

This is a local MCP server that sits between Claude, Codex CLI, ChatGPT Desktop, Cursor, or any MCP host and your existing TradingView tab. It reads charts, writes Pine Script v6, fixes compile errors automatically, manages watchlists, sets alerts, and takes screenshots — all from plain English commands. No API keys, no TradingView credentials, and the AI never trades on your behalf.

• 🖥️ Windows-first portable .exe — single file, no Node.js installer, no registry changes.

• 🔌 Two browser drivers — Playwright/CDP (default) or a loaded Chrome extension.

• 🧠 Autonomous Pine Script repair loop — write → compile → detect error → LLM patch → add-to-chart → verify.

• 🔒 Approval-gated writes — symbol changes, saves, and layout switches wait for your dashboard OK.

• 📰 Optional sentiment/news module — bullish/bearish headline heuristics and financial-news feed (opt-in via TV_ENABLE_SENTIMENT_NEWS=1).

• 📈 Paper-trading backtests — simulated long/short strategy runs, clearly labeled not real trading (Pro/Team/Owner).

• 🌐 Self-contained local dashboard — control, audit log, screenshots, and emergency stop at http://127.0.0.1:3939.

Download the standalone Windows app

Go to the latest release and download tradingview-chrome-mcp.exe.

Put it anywhere — desktop, USB drive, or project folder — and double-click it.

First launch unpacks the embedded Node.js runtime and dependencies to:

%LOCALAPPDATA%\tradingview-chrome-mcp

Subsequent launches reuse that cache and start in seconds. All logs, backups, screenshots, and exports are written there, so the .exe itself is 100% portable.

Related MCP server: TradingView MCP Bridge

Quick start (Windows)

1. Run the .exe

# Default dashboard opens at http://127.0.0.1:3939
.\tradingview-chrome-mcp.exe

The launcher will:

1. Detect or start Chrome.

2. Open the local dashboard.

3. Start the MCP server over STDIO (and an optional HTTP transport if enabled).

2. Register with your AI host

Claude Desktop / Claude Code

Add to %APPDATA%\Claude\claude_desktop_config.json:

{
  "mcpServers": {
    "tradingview-chrome-mcp": {
      "command": "C:\\Users\\%USERNAME%\\AppData\\Local\\tradingview-chrome-mcp\\tradingview-chrome-mcp.exe",
      "env": {
        "TV_DASHBOARD_PORT": "3939",
        "TV_LOG_LEVEL": "info",
        "TV_APPROVAL_TIMEOUT_MS": "120000"
      }
    }
  }
}

Codex CLI

If you used the PowerShell installer, Codex is registered automatically. Otherwise:

codex mcp add tradingview-chrome-mcp "C:\Users\%USERNAME%\AppData\Local\tradingview-chrome-mcp\tradingview-chrome-mcp.exe"

ChatGPT Desktop / Cursor / Windsurf

Point the host at the .exe as an STDIO MCP server with the same environment variables.

3. Ask the AI to trade for you (in words, not money)

Read my TradingView chart and tell me the current symbol and timeframe.

Create a Pine Script v6 EMA crossover indicator called "EMA Cross" and add it to the chart.

Fix all Pine Script compile errors and keep trying until the indicator loads.

Installation options

Full install details: INSTALL.md · Tool reference: TOOL_REFERENCE.md

Chrome extension driver (optional)

The .exe defaults to Playwright over Chrome DevTools Protocol. If you prefer to drive an already-running Chrome instance without --remote-debugging-port, use the Chrome extension driver:

1. Open chrome://extensions and enable Developer mode.

2. Click Load unpacked and select the extension/ folder from this repo.

3. Run the .exe with:

$env:TV_BROWSER_DRIVER = "extension"
$env:TV_EXTENSION_WS_PORT = "9223"
$env:TV_EXTENSION_TOKEN = "tradingview-chrome-mcp"
.\TradingView-Chrome-MCP-0.8.0-portable.exe

The extension connects to the .exe over a local WebSocket, injects MAIN-world scripts into the TradingView tab, and exposes all 53 tools. This is the path that enables the autonomous Pine Script repair loop to catch red compile-error toasts the instant they appear.

Features

Tool categories

The server exposes 60 tools grouped by job:

• Diagnostics — ping, mcp_client_info

• Chart control — tv_status, tv_read_chart, tv_chart_metadata, tv_change_symbol, tv_change_timeframe, tv_ensure_chart

• Pine Script — tv_open_pine_editor, tv_read_pine_source, tv_pine_create, tv_pine_patch, tv_pine_save, tv_pine_add_to_chart, tv_pine_compile_errors, tv_rename_script, tv_pine_backup, tv_pine_list_backups, tv_pine_restore, tv_pine_autofix

• Watchlists — tv_watchlist_read, tv_watchlist_add_symbol, tv_watchlist_sync

• Alerts — tv_alert_create, tv_alert_list, tv_alert_delete

• Layouts — tv_layout_list, tv_layout_switch, tv_layout_save, tv_layout_duplicate, tv_layout_rename, tv_layout_reset, tv_layout_export

• Indicators — tv_indicator_add, tv_indicator_remove, tv_indicator_hide, tv_indicator_show, tv_indicator_settings

• Drawing — tv_drawing_add_trendline

• Verification — tv_chart_verify

• Utilities — tv_screenshot, tv_dismiss_dialogs, tv_read_strategy_tester, tv_chart_data_export, browser_status, browser_list_tabs

• Paper trading — tv_paper_trade

• Safety — emergency_stop, emergency_clear

• Licensing — licence_status, activate_licence, edition_limits

• Audit & Sync — audit_verify, sync_status

Configuration

Set environment variables before launching the .exe:

Example: open directly on XAUUSD

$env:TV_DEFAULT_TRADINGVIEW_URL = "https://www.tradingview.com/chart/?symbol=OANDA%3AXAUUSD"
.\tradingview-chrome-mcp.exe

How the autonomous Pine Script loop works

AI writes Pine Script
        │
        ▼
┌───────────────────────┐
│  MCP .exe (Windows)   │
│  STDIO / HTTP bridge  │
└───────────┬───────────┘
            │ JSON-RPC over WebSocket (extension driver)
            ▼
┌───────────────────────┐
│ Chrome extension       │
│ service worker         │
└───────────┬───────────┘
            │ chrome.scripting.executeScript({ world: "MAIN" })
            ▼
┌───────────────────────┐
│ TradingView tab        │
│ Monaco editor          │
└───────────┬───────────┘
            │ compile error toast appears
            ▼
┌───────────────────────┐
│ error_observer.js      │
│ MutationObserver       │
└───────────┬───────────┘
            │ PINE_SCRIPT_ERROR_DETECTED
            ▼
┌───────────────────────┐
│ MCP .exe receives error│
└───────────┬───────────┘
            │ error text passed to AI
            ▼
AI patches code and retries

Building the .exe from source

On a Windows machine with Node.js 22.5+ (24+ recommended):

git clone https://github.com/firyomaefx/tradingview-chrome-mcp.git
cd tradingview-chrome-mcp
npm install
npm run build:exe

Outputs:

• TradingView-Chrome-MCP-0.8.0-portable.exe (~1.2 GB) — single-file portable app.

• TradingView-Chrome-MCP-0.8.0-windows-setup.exe (~1.2 GB) — classic Windows installer.

Both embed Node.js, the compiled server, and all runtime dependencies via caxa. The setup .exe is produced only if Inno Setup 6 or 7 is installed.

Run from source (no .exe)

For development or non-Windows platforms. Requires Node.js 22.5+ (24+ recommended) — the server uses the built-in node:sqlite module, which is missing in Node 20. On an unsupported Node it prints an actionable upgrade message and exits.

git clone https://github.com/firyomaefx/tradingview-chrome-mcp.git
cd tradingview-chrome-mcp
npm install                       # no native deps; no build tools required
npx playwright install chromium   # only needed for the default playwright driver
npm run build                     # required: dist/ is gitignored and not shipped
npm start                         # MCP server over STDIO; boots with zero config

The server starts with no .env at all. To customize ports, Chrome path, cloud sync, or the LLM key: cp .env.example .env and edit. See INSTALL.md Option C for the launcher-with-shortcuts flow.

Architecture

┌─────────────────┐      STDIO / HTTP       ┌──────────────────────┐
│  MCP host       │  ───────────────────────▶  │  tradingview-chrome  │
│  (Claude, Codex,│                           │  -mcp.exe             │
│  ChatGPT, etc.) │                           │                      │
└─────────────────┘                           │  ┌───────────────┐   │
                                              │  │ Tool registry │   │
                                              │  │ Policy +      │   │
                                              │  │ approvals     │   │
                                              │  └───────┬───────┘   │
                                              │          │           │
                                              │  ┌───────▼───────┐   │
                                              │  │ Browser driver│   │
                                              │  │ (Playwright   │   │
                                              │  │  or extension)│   │
                                              │  └───────┬───────┘   │
                                              └──────────┼───────────┘
                                                         │
                                              ┌──────────▼──────────┐
                                              │  Google Chrome      │
                                              │  TradingView tab    │
                                              └─────────────────────┘

Read ARCHITECTURE.md for diagrams, invariants, and transport details.

Security & privacy

• No credential storage. Cookies, tokens, and passwords are never read or transmitted.

• Temporary Chrome profile by default. Isolated unless you opt into TV_ALLOW_REAL_PROFILE=1.

• Dashboard bearer token. All dashboard API calls require Authorization: Bearer <TV_DASHBOARD_TOKEN>.

• Local-only audit logs. Every action is written to logs/audit.jsonl with sensitive inputs redacted.

• Approval-gated writes. Destructive tools require explicit dashboard approval.

• Emergency stop. Instantly disables all tool execution.

• Domain allowlist. Browser tools only run on tradingview.com / www.tradingview.com.

• No remote telemetry in local mode. The Vercel-hosted fork is separate and opt-in.

Project layout

tradingview-chrome-mcp/
├── src/                    # Local MCP server
│   ├── server/             # STDIO + HTTP transports
│   ├── tools/              # Tool registry (60 tools)
│   ├── adapters/           # TradingView DOM automation
│   ├── browser/            # Playwright + extension drivers
│   ├── dashboard/          # Local Express control panel
│   ├── permissions/        # Policy + approval queue
│   ├── detect/             # MCP host client detection
│   ├── telemetry/          # Privacy-first telemetry helpers
│   └── config.ts           # Centralized config
├── extension/              # Optional Chrome extension (MV3)
├── scripts/                # Launchers, installer (Inno Setup .iss)
├── vercel-hosted/          # Separate Vercel SSE fork
├── tests/                  # Unit + integration tests
└── docs/                   # README, INSTALL, HOSTED, etc.

Development status

• Version: 0.8.0

• Default branch: main

• Local tests: 123 passing

• CI: .github/workflows/ci.yml runs Windows and Ubuntu jobs on every push.

License

MIT. See LICENSE.