TradingView MCP

A local MCP bridge and CLI for inspecting and controlling TradingView Desktop charts, developing Pine Scripts, and practicing with chart replay.

The original tradingview-mcp was created by @tradesdontlie. This checkout adds local connection handling, launchers, and integration improvements.

One-Shot Setup

Paste this into Claude Code or Codex running locally on the computer with TradingView Desktop. The agent needs terminal and file access; a cloud-only chat cannot reach your desktop's local debug port.

Set up TradingView MCP for the local client I am using (Claude Code or Codex).
Repository: https://github.com/madiver/TradingView-MCP
First read the setup guide: https://raw.githubusercontent.com/madiver/TradingView-MCP/main/SETUP_GUIDE.md

Reuse an existing checkout only after verifying it is this repository; otherwise clone that URL into a stable folder such as ~/TradingView-MCP. Do not overwrite another folder or discard local changes. Check Git and a supported Node.js version, then run npm ci in the checkout.

Follow the setup guide's instructions for my OS and this client. Reuse a working debug launcher if already configured; otherwise use the correct native Mac/Windows launcher from https://github.com/madiver/TradingView-MCP/releases/latest, or the documented Linux launch steps. Keep TradingView sign-in and save prompts under my control.

Register the local stdio server using absolute paths to Node and src/server.js. Use claude mcp add for Claude Code or codex mcp add / the Codex TOML configuration for Codex. Inspect any existing tradingview entry, preserve other servers and settings, and retain a custom local debug port if already configured. If you cannot identify the client, ask which one to configure.

Verify the client registration and run npm run tv -- status. Tell me if I need to reconnect or restart the client. After its tools are available, call tv_health_check and chart_get_state without changing my chart. Report separately whether configuration is saved and whether the live chart connection has been verified; do not claim success for checks you could not run.

The same prompt works without an existing checkout. Follow SETUP_GUIDE.md for manual steps, Windows commands, both configuration formats, and reconnect instructions.

Related MCP server: TradingView MCP Bridge

Prerequisites

• TradingView Desktop app, signed in with the required chart/data permissions

• A supported Node.js LTS: 22, 24, or 26 (.nvmrc selects 24)

• Git to clone the repository for MCP setup

• An MCP client with local stdio support, such as Claude Code or Codex, or a terminal for the CLI

• macOS, Windows, or Linux

Quick Start

Standalone Mac Intel, Mac Apple silicon, Windows Intel/AMD, and Windows ARM launchers are available in GitHub Releases. They need TradingView Desktop, but no developer tools. See installation and sharing instructions. Install the MCP server separately using the steps below when you want AI chart tools.

1. Clone and install

For a new installation, clone the public repository to a stable folder, then install the locked dependencies:

git clone https://github.com/madiver/TradingView-MCP.git
cd TradingView-MCP
npm ci

If you already have a checkout, verify its remote and use it without discarding local work. See SETUP_GUIDE.md for home-directory and Windows examples.

2. Launch TradingView with CDP

TradingView must be running with the debug port enabled.

macOS: download the Intel or Apple silicon launcher from Releases, extract it, and drag TradingView Debug.app to Applications. Use that app from Finder or the Dock; the download needs no Python or Xcode. See installation instructions.

To build and install from source instead:

python3 launcher/install.py

The source installer requires Python 3 and Xcode Command Line Tools (swiftc). Both versions request a graceful restart and respect save prompts. See launcher instructions.

Windows: use the standalone TradingView Debug launcher. It supports graceful restarts, verifies the connection, and can be shared without this repository. The legacy batch entry point runs the installed launcher:

scripts\launch_tv_debug.bat

Linux: start TradingView with the local debug flags. Quit any existing non-debug instance through its UI first:

/path/to/tradingview --remote-debugging-address=127.0.0.1 --remote-debugging-port=9222

The legacy shell launch scripts terminate matching processes; they do not provide the native launchers' save-prompt handling. Linux chart automation has not been qualified against an installed Desktop app in this checkout.

Or use the MCP tool after setup: "Use tv_launch to start TradingView in debug mode"

3. Register the MCP server

Choose Claude Code or Codex, and replace the example paths with the actual absolute paths. Use node -p "process.execPath" to find your Node executable; a desktop client may not inherit your terminal's PATH. Register only the client you intend to use, or configure each separately if you use both.

Claude Code (user-scoped stdio server):

claude mcp add --scope user --transport stdio tradingview --env TV_CDP_HOST=127.0.0.1 --env TV_CDP_PORT=9222 -- "/absolute/path/to/node" "/absolute/path/to/TradingView-MCP/src/server.js"
claude mcp get tradingview

Codex (local stdio server):

codex mcp add tradingview --env TV_CDP_HOST=127.0.0.1 --env TV_CDP_PORT=9222 -- "/absolute/path/to/node" "/absolute/path/to/TradingView-MCP/src/server.js"
codex mcp get tradingview

Keep an existing custom port in place of 9222. Claude Code uses ~/.claude.json for user-scoped servers; Codex uses ~/.codex/config.toml by default. Codex desktop/CLI/IDE clients on the same host share configuration. If the CLI is unavailable, merge the matching JSON or TOML entry from SETUP_GUIDE.md; do not paste JSON into Codex's TOML file. That guide also includes native Windows PowerShell examples.

Official references: Claude Code MCP, Codex MCP.

4. Verify

Check claude mcp get tradingview or codex mcp get tradingview, then use /mcp in the corresponding terminal client to inspect available tools. Reconnect or restart your client if needed; registration alone does not make tools available in an already-running chat.

Ask: "Use tv_health_check and chart_get_state to verify the connection without changing my chart." A ready chart should report cdp_connected: true and api_available: true. If the tools are not loaded yet, npm run tv -- status can check the local connection, but client setup remains unverified until its tools work.

What This Tool Does

• Pine Script development — write, inject, compile, debug scripts with AI

• Chart navigation — change symbols, timeframes, zoom to dates, add/remove indicators

• Visual analysis — read indicator values, price levels, drawn levels from custom indicators

• Draw on charts — trend lines, horizontal levels, rectangles, text

• Manage alerts — create, list, delete price alerts

• Replay practice — step through historical bars, practice entries and exits with P&L tracking

• Screenshots — capture chart state

• Multi-pane layouts — 2x2, 3x1 grids with different symbols per pane

• Stream data — JSONL output from your live chart for monitoring scripts

• CLI access — every tool is also a tv command, pipe-friendly JSON output

Choosing Tools

The server advertises tool-selection instructions. AGENTS.md and CLAUDE.md provide repository-specific guidance for coding agents.

Tool Reference

Chart Reading

Custom Indicator Data (Pine Drawings)

Read line.new(), label.new(), table.new(), box.new() output from any visible Pine indicator.

Always use study_filter to target a specific indicator: study_filter: "MyIndicator".

Chart Control

Pine Script Development

Replay Mode

Multi-Pane, Alerts, Drawings, UI

Tool behavior

quote_get with a different symbol temporarily switches the bound chart and restores it. Strategy-report tools may open the Strategy Tester and make a hidden strategy visible; their results report that change. Alert creation/deletion changes actual TradingView alerts. Replay trades are practice actions, and the project does not place live broker/exchange orders.

Connections stay bound to their selected tab during an operation. Use tab_follow_visible between operations to attach to the chart currently visible; avoid switching targets during a drawing run. The default debug endpoint is 127.0.0.1:9222. Match TV_CDP_PORT to any custom launcher port and keep the endpoint local.

Tests and development

npm ci
npm run check       # JavaScript syntax checks
npm test            # offline tests and MCP startup; no Desktop chart changes
npm run test:network # opt-in Pine compilation API tests; requires internet
npm run test:e2e    # opt-in Desktop tests; changes chart state

Use a disposable TradingView layout for E2E tests. npm run test:all explicitly includes both network and Desktop suites. CI runs offline tests on Linux, macOS, and Windows with Node 22/24/26, plus launcher checks. See CONTRIBUTING.md for the validation matrix and .NET 10 launcher tests.

CLI Commands

tv status                          # check connection
tv quote                           # current price
tv symbol BTCUSD                   # change symbol
tv ohlcv --summary                 # price summary
tv screenshot -r chart             # capture chart
tv pine compile                    # compile Pine Script
tv pane layout 2x2                 # 4-chart grid
tv stream quote | jq '.close'      # monitor price ticks

Full command list: tv --help

Troubleshooting

Architecture

MCP Client  ←→  MCP Server (stdio)  ←→  CDP (port 9222)  ←→  TradingView Desktop (Electron)

• Transport: MCP over stdio + CLI (tv command)

• Connection: Chrome DevTools Protocol on localhost:9222

• Local chart connection — chart tools use CDP; symbol search, Pine compilation, and alerts can use TradingView endpoints

• Dependencies: MCP SDK, Chrome DevTools client, and Zod; versions are locked in package-lock.json

This checkout selectively incorporates input-handling and reliability fixes from upstream commit c05b8f5. Local visible-tab selection, explicit target binding, the macOS debug launcher, and TVLevels integration are retained. npm run test:unit runs the regression suite without changing a live TradingView chart. Chart-mutating E2E tests remain separate.

Credits

Original TradingView MCP author: @tradesdontlie. The original repository provides the foundation for this project. Its copyright and license notices are retained. See PROVENANCE.md for source lineage and the clean-history boundary.

Disclaimer

This project is provided for personal, educational, and research purposes only.

This tool uses the Chrome DevTools Protocol (CDP), a standard debugging interface built into all Chromium-based applications. Chart operations use the locally running Desktop app; symbol search, Pine compilation, and alert management can also use TradingView endpoints. Account permissions and access controls remain applicable. The debug port must be explicitly enabled by the user via a standard Chromium command-line flag.

By using this software you agree that:

1. You are solely responsible for ensuring your use complies with TradingView's Terms of Use and all applicable laws.

2. This tool accesses undocumented internal TradingView APIs that may change at any time.

3. This tool must not be used to redistribute, resell, or commercially exploit TradingView's market data.

4. The authors are not responsible for any account bans, suspensions, or other consequences.

Use at your own risk.

License

MIT — see LICENSE. Applies to source code only, not to TradingView's software, data, or trademarks.