How to connect Claude to your TradingView charts

Install the TradingView MCP bridge for me and get it working end to end. The repo is https://github.com/tradesdontlie/tradingview-mcp and it connects you to my locally running TradingView Desktop app over the Chrome DevTools Protocol on port 9222.

Do this in order and tell me what you are doing at each step.

1. Check that I have Node.js 18 or newer by running node --version. If I do not, stop and tell me instead of continuing.

2. Clone the repo into ~/tradingview-mcp, cd into it, and run npm install. Show me any errors in full rather than summarising them.

3. Register it with Claude Code as a stdio MCP server named tradingview, pointing at src/server.js inside that folder using the absolute path, never a relative one. Show me the exact command you ran and the resulting config entry.

4. Launch TradingView Desktop with remote debugging enabled, using the launch script in the repo's scripts folder for my operating system. If TradingView is already running without the debug flag, tell me to quit it completely first, because that flag only applies at launch and a running instance will not pick it up.

5. Run tv_health_check and show me the raw result. If it fails, diagnose it properly: check whether port 9222 is listening, whether the desktop app is actually running, and whether the server shows as connected in claude mcp list. Do not tell me the setup succeeded until the health check passes.

At the end, list the tools you now have available and give me three example things I could ask you to do with my chart.

Read my current TradingView chart and tell me what is actually on it: the symbol, the timeframe, the recent price action, and any indicators I already have loaded. Then identify the clearest support and resistance levels in the visible range and draw each one onto the chart as a horizontal line labelled with its price. Explain in plain language why you chose each level, and tell me which ones you consider weak, so I am judging your reasoning rather than trusting a line because it appeared.

Write me a Pine Script indicator that does this: [describe it in one sentence, for example "a 14-period RSI that shades the chart background when it crosses above 70 or below 30"]. Inject it into my TradingView Pine editor, compile it, and fix any compilation errors yourself before you show me anything. Then add an alert condition for each of those states so I am notified without watching the screen, and tell me exactly what I still need to click inside TradingView to activate the alert, since that part is not something you can do for me.

Read my TradingView watchlist, then work through each symbol one at a time on the daily timeframe and record where price is sitting relative to its 50 and 200 period moving averages, plus whether it is near a recent high or low. Build me one table at the end, ranked from cleanest setup to messiest, with a single sentence of reasoning per row. Tell me up front roughly how long this will take given the number of symbols, and skip any symbol whose data does not load rather than filling it in with a guess.

Turn this idea into a Pine Script strategy so I can test it rather than believe it: [describe the entry, the exit, and the stop in one or two sentences]. Write it, inject it into my Pine editor, compile it, and fix any errors before showing me. Then tell me where to read the results in TradingView's Strategy Tester panel, which numbers actually matter (net profit, max drawdown, number of trades, profit factor), and how few trades would make the whole result statistically meaningless.

Set my chart to [symbol] on the [timeframe] and start bar replay from [date] so I can practise reading price without knowing what happens next. Step forward one bar at a time whenever I say next, and do not reveal anything beyond the current bar under any circumstances, including in your commentary. When I call an entry, log my reasoning as I gave it, then keep stepping and afterwards tell me what actually happened and what a disciplined exit would have looked like compared to what I said.