Teaching Claude to read charts through Electron's debug port

What it does

This is a local bridge that exposes your TradingView Desktop application to Claude Code through the Chrome DevTools Protocol. It surfaces 78 structured tools that let an AI read chart data and indicator values, inject and compile Pine Script, manage layouts, draw annotations, take screenshots, and step through historical replay bars. All processing stays on your machine; the tool does not connect to TradingView’s servers or redistribute market data.

The interesting bit

Rather than scraping APIs or reverse-engineering network traffic, it attaches to TradingView’s Electron shell via the standard Chromium debug port, treating the desktop app like a local browser. That makes the entire UI state—indicator tables, line drawings, session labels—legible to an agent without ever leaving localhost. The authors frame the project as open research into how LLMs handle ambiguous, real-time financial UI state, not as a production trading bot.

Key highlights

• 78 MCP tools covering chart reading, symbol and timeframe switching, multi-pane layouts, alerts, and screenshots
• Full Pine Script development loop: inject source, compile, catch errors, read console output, and save to TradingView cloud
• Runs fully offline after setup: polls the Electron debug port on localhost, so no market data leaves your machine
• Also ships as a pipe-friendly CLI emitting JSON for shell scripting and local monitoring
• Includes a decision tree (CLAUDE.md) that teaches Claude which tool sequence to use for common requests like “What’s on my chart?” or “Give me a full analysis”

Caveats

• Requires a paid TradingView subscription and the Desktop app; it does not bypass any paywall
• Relies on undocumented internal APIs exposed through the Electron debug interface, so any TradingView update can break functionality without warning
• Programmatic consumption of chart data may conflict with TradingView’s Terms of Use

Verdict

A solid experiment for traders and researchers who want to automate Pine Script workflows or explore LLM-assisted technical analysis. Avoid it if you need an officially supported, stable API or a system that executes real trades.