TradingView MCP

MCP server for TradingView Desktop — 78 tools to read, control, and automate charts via Chrome DevTools Protocol.

Built on top of tradingview-mcp by @tradesdontlie and the Jackson fork by @LewisWJackson. This fork adds security hardening, input sanitization, bug fixes, and code quality improvements.

What's New in This Fork

One-Shot Setup

Paste this into Claude Code and it will handle everything:

Set up TradingView MCP for me.
Clone https://github.com/ulianbass/tradingview-mcp.git to ~/tradingview-mcp, run npm install, then add it to my MCP config at ~/.claude/mcp.json (merge with any existing servers, don't overwrite them).
The config block is: { "mcpServers": { "TradingView MCP": { "command": "node", "args": ["/Users/YOUR_USERNAME/tradingview-mcp/src/server.js"] } } } — replace YOUR_USERNAME with my actual username.
Then copy rules.example.json to rules.json and open it so I can fill in my trading rules.
Finally restart and verify with tv_health_check.

Or follow the manual steps below.

Prerequisites

• TradingView Desktop app (paid subscription required for real-time data)

• Node.js 18+

• Claude Code (for MCP tools) or any terminal (for CLI)

• macOS, Windows, or Linux

Quick Start

1. Clone and install

git clone https://github.com/ulianbass/tradingview-mcp.git ~/tradingview-mcp
cd ~/tradingview-mcp
npm install

2. Set up your rules

cp rules.example.json rules.json

Open rules.json and fill in:

• Your watchlist (symbols to scan each morning)

• Your bias criteria (what makes something bullish/bearish/neutral for you)

• Your risk rules (the rules you want Claude to check before every session)

3. Launch TradingView with CDP

TradingView must be running with the debug port enabled.

Mac:

./scripts/launch_tv_debug_mac.sh

Windows:

scripts\launch_tv_debug.bat

Linux:

./scripts/launch_tv_debug_linux.sh

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

4. Add to Claude Code

Add to ~/.claude/.mcp.json (merge with any existing servers):

{
  "mcpServers": {
    "TradingView MCP": {
      "command": "node",
      "args": ["/Users/YOUR_USERNAME/tradingview-mcp/src/server.js"]
    }
  }
}

Replace YOUR_USERNAME with your actual username. On Mac: echo $USER to check.

5. Verify

Restart Claude Code, then ask: "Use tv_health_check to verify TradingView is connected"

6. Run your first morning brief

Ask Claude: "Run morning_brief and give me my session bias"

Or from the terminal:

npm link  # install tv CLI globally (one time)
tv brief

Morning Brief Workflow

This is the feature that turns this from a toolkit into a daily habit.

Before every session:

1. TradingView is open (launched with debug port)

2. Run: tv brief in your terminal (or ask Claude: "run morning_brief")

3. Claude scans every symbol in your watchlist, reads your indicator values, applies your rules.json criteria, and prints:

BTCUSD  | BIAS: Bearish  | KEY LEVEL: 94,200  | WATCH: RSI crossing 50 on 4H
ETHUSD  | BIAS: Neutral  | KEY LEVEL: 3,180   | WATCH: Ribbon direction on daily
SOLUSD  | BIAS: Bullish  | KEY LEVEL: 178.50  | WATCH: Hold above 20 EMA

Overall: Cautious session. BTC leading bearish, SOL the exception — watch for divergence.

4. Save it: "save this brief" (uses session_save)

5. Next morning, compare: "get yesterday's session" (uses session_get)

What This Tool Does

• Morning brief — scan watchlist, read indicators, apply your rules, print session bias

• 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

How Claude Knows Which Tool to Use

Claude reads CLAUDE.md automatically when working in this project. It contains the full decision tree.

Tool Reference (81 MCP tools)

Morning Brief (new in this fork)

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

CLI Commands

tv brief                           # run morning brief
tv session get                     # get today's saved brief
tv session save --brief "..."      # save a brief

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

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

• 78 original tools + 3 morning brief tools = 81 MCP tools total

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

• Connection: Chrome DevTools Protocol on localhost:9222

• No external network calls — everything runs locally

• Zero extra dependencies beyond the original

Credits

• Original tradingview-mcp by @tradesdontlie — the foundation

• Jackson fork by @LewisWJackson — morning brief, rules config, launch fix

• Security hardening and bug fixes by @ulianbass

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. It does not reverse engineer any proprietary TradingView protocol, connect to TradingView's servers, or bypass any access controls. 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.