What is TradingView MCP Bridge?
TradingView MCP Bridge, by the GitHub user tradesdontlie, connects Claude Code or another MCP client to a TradingView Desktop app running on your machine. It does not use a TradingView API; it attaches to the Electron app through the Chrome DevTools Protocol on localhost port 9222, which you enable by launching TradingView with --remote-debugging-port=9222. It is not affiliated with TradingView, needs a paid TradingView subscription for real-time data, and cannot place real trades.
The server registers 84 tools for reading chart state, indicator values and Pine Script drawings (lines, labels, tables, boxes), changing symbol and timeframe, writing and compiling Pine Script, drawing shapes, managing alerts and watchlists, multi-pane layouts, replay practice and screenshots; every tool is also a tv command-line call. The repository has about 7,030 stars, an MIT licence file, and no tagged releases; its last commit to main was on 28 July 2026.
How to install TradingView MCP Bridge
git clone https://github.com/tradesdontlie/tradingview-mcp.git && npm install, then node src/server.jsIs TradingView MCP Bridge worth it?
This is the most-starred TradingView MCP server for a reason: it reaches the chart you are already looking at, including the output of private and paid Pine indicators, which no API exposes. Reading a session table, the levels a custom indicator draws or the current RSI is a single tool call, and the output is trimmed for context: lines are deduplicated, labels capped at 50 per study, and a typical 'analyse my chart' run is about 5 to 10 KB rather than 80 KB, per the README. For Pine Script authors the write, compile, read errors and fix loop is the strongest workflow.
The foundation is fragile by design. The tool uses undocumented internal TradingView interfaces through the Electron debug port, and the README itself says they can change or break with any update and advises pinning your TradingView version. The issue tracker bears that out: many of the 66 open issues are launch failures on TradingView Desktop 3.x and on Microsoft Store (MSIX) installs, where the debug port will not bind, alongside tools such as layout_switch and draw_shape reporting success without effect. About 200 pull requests sit open, and nothing has merged since late July.
The terms risk is real and the authors say so. TradingView's Terms of Use restrict automated data collection, scraping and non-display use, and the disclaimer states the tool may conflict with them and that you bear the risk of account bans. It forbids redistributing data and using it for automated trading. The streaming commands that poll your chart into JSONL are exactly the kind of use those terms address.
The security exposure is the debug port. Chrome DevTools on 9222 gives any local process full control of the TradingView app, signed-in session included, and ui_evaluate runs arbitrary JavaScript inside it. For market data an agent can rely on, atilaahmettaner/tradingview-mcp takes a different route, with screeners, technical analysis and backtests over public data and a hosted option, at the cost of never seeing your own chart.
Where it earns its place
A Pine Script developer who sells indicators to subscribers
Fix compile errors and iterate on a 1,000-line script faster
Let Claude Code call pine_set_source, pine_smart_compile and pine_get_errors in a loop and read log output with pine_get_console. Free on top of the TradingView plan; pine_get_source can return 200 KB or more, so avoid reading whole scripts repeatedly.
A futures day trader using a custom session-levels indicator
Get a morning summary of the levels and indicator values on four charts
Set a 2x2 layout with pane_set_symbol, then read data_get_pine_lines and data_get_pine_tables with a study_filter for each pane. The assistant summarises; the trader decides, since automated trading on this data is barred by the disclaimer.
A trading educator practising entries with students
Replay a historical session bar by bar and discuss each decision
Start replay_start at a date, replay_step through bars and log practice trades with replay_trade and replay_status for P&L. No real orders are placed.
Before you commit
- Setup
- Clone the repo, npm install (Node.js 18+), launch TradingView Desktop with --remote-debugging-port=9222 using the bundled script or tv_launch, add node /path/to/src/server.js to Claude Code's .mcp.json, then run tv_health_check. Windows Store installs often fail to open the debug port.
- Integrations
- 84 tools: chart reading (chart_get_state, data_get_study_values, quote_get, data_get_ohlcv), Pine drawing readers, chart control, panes and tabs, Pine Script development, replay, drawing, alerts, watchlists, layouts, screenshots and UI automation (ui_click, ui_evaluate). The tv CLI mirrors them.
- Data and privacy
- Works only on the local app; the tool itself sends nothing to TradingView's servers, though pine_save writes to your TradingView cloud account. Chart data goes to your model provider through the client. Port 9222 lets any local process control the logged-in app, and ui_evaluate executes arbitrary JavaScript. Pine labels and tables written by third-party indicators are untrusted text in the model's context.
- Cost at scale
- Free code; you pay for a TradingView subscription with real-time data. Token use per full chart analysis is about 5 to 10 KB of tool output, per the README.
- Limits
- Undocumented interfaces break on TradingView updates; 66 open issues, mostly Windows and Desktop 3.x launch failures; about 200 open pull requests and no merge since July 2026. No real trade execution.
What’s good
- Reads your own chart, including private Pine indicators
- Pine Script write, compile and debug loop
- Compact outputs keep chart analysis around 5 to 10 KB
- Every tool doubles as a tv CLI command
What’s not
- Relies on undocumented internals that break on updates
- May conflict with TradingView's Terms of Use
- Debug port 9222 exposes the whole app to local processes
- Launch fails on many Windows Store installs
Best for
Discretionary traders and Pine Script developers who want an assistant on their own chart and accept the terms and breakage risk.
TradingView MCP Bridge alternatives
TradingView MCP Bridge: common questions
- Is TradingView MCP Bridge worth it?
- Clever and popular, but it runs on undocumented internals of an app whose terms restrict automation, so treat it as a personal research tool that can break or get an account flagged. We rate it 3.5 out of 5.
- How much does TradingView MCP Bridge cost?
- Free and open source (MIT). Requires TradingView Desktop and a TradingView subscription.
- What are the downsides of TradingView MCP Bridge?
- Relies on undocumented internals that break on updates; may conflict with TradingView's Terms of Use; debug port 9222 exposes the whole app to local processes; launch fails on many Windows Store installs.
- Who is TradingView MCP Bridge best for?
- Discretionary traders and Pine Script developers who want an assistant on their own chart and accept the terms and breakage risk.
- How much does TradingView MCP Bridge cost for a team or in production?
- Free code; you pay for a TradingView subscription with real-time data. Token use per full chart analysis is about 5 to 10 KB of tool output, per the README.
- Is TradingView MCP Bridge safe for company data?
- Works only on the local app; the tool itself sends nothing to TradingView's servers, though pine_save writes to your TradingView cloud account. Chart data goes to your model provider through the client. Port 9222 lets any local process control the logged-in app, and ui_evaluate executes arbitrary JavaScript. Pine labels and tables written by third-party indicators are untrusted text in the model's context.
- What are the best TradingView MCP Bridge alternatives?
- The closest alternatives we have reviewed are Chrome DevTools MCP and Plaid MCP servers.
Answers checked Oct 31, 2026.