What it does

TradingView MCP Bridge is a Node.js server that exposes 78+ tools to Claude Code (or any MCP client) by attaching to your locally running TradingView Desktop app through Chrome DevTools Protocol. It can read indicator values, switch symbols, draw lines, compile Pine Script, take screenshots, and stream bar data — all without touching TradingView’s servers or APIs.

The interesting bit

The project treats a closed commercial Electron app as an LLM-readable environment by poking at its internal debug interface. The authors frame this as open research into “how LLM-based agents interact with professional trading interfaces,” complete with a RESEARCH.md file on failure modes and latency constraints. It’s essentially a very elaborate, very fragile screen-scraper that happens to speak JSON.

Key highlights

• 78 MCP tools covering chart navigation, Pine Script injection, multi-pane layouts, alerts, replay mode, and UI interaction
• All data stays local; no TradingView credentials or market data leaves your machine
• Full CLI mirror (tv <command>) with JSON output for piping to jq
• Auto-detects and launches TradingView with --remote-debugging-port=9222 on macOS, Windows, and Linux
• Includes a CLAUDE.md decision tree so Claude knows which tool chain to invoke for common requests

Caveats

• Requires a paid TradingView subscription and the Desktop app; won’t bypass paywalls
• Uses undocumented internal APIs that “can change or break without notice in any TradingView update”
• Programmatic data consumption may conflict with TradingView’s Terms of Use; the README explicitly warns you are “solely responsible” for compliance
• Not a trading bot — chart interaction only, no real trade execution

Verdict Worth a look if you’re a TradingView power user who wants to automate chart workflows or experiment with LLM-assisted Pine Script development. Skip it if you need reliability, don’t have a paid subscription, or were hoping for an official API.