Since September 2026, TradingView runs its own MCP server, so Claude can pull quotes, screeners, technical ratings, news and alerts from your account. It can’t see the chart you have open. Here is the setup, the routes that can see your chart, and what TradingView’s Terms allow.
November 15, 2026
15
min to read
The short answer
Add TradingView’s official MCP server, in public beta since September 16, 2026, as a Claude connector and sign in. On Essential plans and up, Claude can pull quotes, price bars, screeners, technical ratings, news, filings and alerts. It can’t see your open chart or place orders, its data is delayed, and TradingView’s Terms forbid automated trading with it.
MCP, the Model Context Protocol, is the open standard Anthropic introduced on November 25, 2024 for “secure, two-way connections” between data sources and AI tools. A company or a developer writes an MCP server: a program that offers tools such as “get price history” or “create alert.” Claude is the client. In TradingView’s words, the AI client “decides which MCP Server tools to call, and generates the responses you see.” Claude asks for your approval before it uses a tool, unless you have told it to always allow that tool.
Servers come in two kinds, and the difference matters for your safety:
MCP gives Claude access, not judgment. The data is only as good as the server that sends it, and the reading is only as good as Claude’s reading of it.
The phrase now covers four different things, and they see very different data:
| Route | Made by | Sees the chart you have open | What it reads | Setup |
|---|---|---|---|---|
| TradingView MCP Server | TradingView, official, in beta | No | Quotes, price bars, screener, technical ratings, fundamentals, news, filings, calendars, watchlists, price alerts | Add a URL and sign in; Essential plan or higher |
| TradingView AI Copilot | TradingView, inside its charts | Yes | Your chart plus TradingView data; Claude Sonnet 5.5 is one of three models you can pick | A paid add-on to a paid TradingView plan |
| Community data server, such as atilaahmettaner/tradingview-mcp | An independent developer | No | TradingView screener and technical data through open-source libraries, plus Yahoo Finance prices | Python and a config file |
| Community desktop bridge, such as tradesdontlie/tradingview-mcp | An independent developer | Yes, in TradingView Desktop | Your chart’s symbol, timeframe, indicator values and Pine drawings | Node.js, Claude Code and TradingView Desktop started in debug mode |
Which one fits depends on the job:
The no-setup option is a screenshot of your chart pasted into Claude. Our guide to AI chart analysis tests how well that actually works, screenshot against real data. We cover what Claude can and can’t do with that, and with a broker, in can Claude trade for you.
You need a TradingView plan at Essential or above. TradingView’s MCP docs say trial plans don’t include MCP access. On Claude’s Free plan you can add one custom connector. Then:
TradingView says its server is listed in Claude’s connector directory, so you can search for TradingView in Claude’s Customize menu. Or add it by hand: in Customize, then Connectors, choose “+ Add,” then “Add custom connector,” and paste https://mcp.tradingview.com/mcp.
Claude opens TradingView’s own sign-in page in your browser. Approve access there. Sign-in uses OAuth, so there is no API key to copy or store.
Open the connector and read the list. TradingView marks each tool as read-only, which never changes your account, or write, which creates, changes or deletes watchlists and alerts.
Start with something you can verify on your own chart, such as the last daily close of a symbol you know.
The connector works in Claude on the web, on the desktop and on your phone once it is added. In Claude Code, TradingView’s docs give one command: claude mcp add --transport http mcp-tradingview https://mcp.tradingview.com/mcp. Then type /mcp and authorize with your TradingView account in the browser.
Tool calls are limited to about 100 a minute per user. To disconnect, remove the connector in Claude, and revoke Claude’s access in TradingView under Settings, then Connected apps, as its Terms describe.
On November 14, 2026, TradingView’s docs listed 35 tools in nine groups. In a trader’s terms:
| Group | Tools | What Claude gets |
|---|---|---|
| Market data | 3 | Price bars from 1-minute to monthly, up to 5,000 per call, and economic series such as US inflation |
| Screener | 5 | TradingView’s screener with filters and presets, quotes for up to 50 symbols at once, and a technical ratings snapshot per timeframe |
| Symbol search | 1 | Turns a company name into an exchange and ticker |
| Fundamentals and forecasts | 3 | Valuation, margins, growth, reported history and analyst consensus |
| Documents | 2 | 10-K, 10-Q and 8-K filings and earnings call transcripts |
| News | 2 | Headlines for a symbol and the full text of a story |
| Calendars | 3 | Earnings, economic releases and dividends |
| Watchlists | 8 | List, create, edit and delete your watchlists |
| Alerts | 8 | Create, pause, edit and delete simple price alerts, and read when they fired |
The technical ratings tool is the closest thing to reading indicators. For one symbol on one timeframe, it returns RSI, Stochastic, CCI, ADX, MACD, momentum, the Awesome Oscillator, moving averages from 10 to 200 periods, VWMA and Hull MA, plus TradingView’s summary ratings. Ask for it on several timeframes and Claude can line them up for you.
What it can’t do, according to the same docs and TradingView’s launch post:
Search GitHub for “tradingview mcp” and you get dozens of projects. None is made by TradingView, and their capabilities are what their READMEs say: check them yourself. Most fall into two groups.
atilaahmettaner/tradingview-mcp is an MIT-licensed Python server with 39 tools: screeners, multi-timeframe technical analysis, backtests of nine built-in strategies, news and sentiment, across crypto exchanges and stock markets. Its README calls it an “independent open-source project” that is “not affiliated with, endorsed by, or associated with TradingView Inc.” It needs no TradingView account. It gets TradingView screener and technical data through two open-source libraries, tradingview-ta and tradingview-screener, adds prices from Yahoo Finance, and can add news through a free Marketaux key. One part of the README calls its data live; another warns that “market data may be delayed, inaccurate, or incomplete.” Treat it as unverified until it matches your chart.
To install it in Claude Desktop, following its README and the MCP project’s guide to local servers:
The README asks for Python 3.10 to 3.13, since 3.14 is not supported yet, and runs the server with uvx, the runner that comes with Astral’s uv.
Run pip install tradingview-mcp-server. Get it only from that repository or its PyPI package: the README warns that copies under other accounts have shipped malware.
From the Claude menu in your computer’s menu bar, open Settings, then Developer, then Edit Config. On a Mac the file is ~/Library/Application Support/Claude/claude_desktop_config.json; on Windows it is %APPDATA%\Claude\claude_desktop_config.json.
Paste the block below, with your own username in the path. The README says Claude Desktop on a Mac may not find uvx without its full path.
Quit Claude Desktop completely and open it again. Click “Add files, connectors, and more” at the bottom left of the chat box, then Connectors, and the server should be listed with its tools.
{ "mcpServers": { "tradingview": { "command": "/Users/YOUR_USERNAME/.local/bin/uvx", "args": ["--from", "tradingview-mcp-server", "tradingview-mcp"] } } }
tradesdontlie/tradingview-mcp takes the other approach. It connects Claude Code to the TradingView Desktop app on your computer through the Chrome DevTools Protocol, a debugging interface built into Chromium-based apps that you turn on by starting TradingView with a debug port. According to its README, its 78 tools read what is on your chart: the symbol and timeframe, the values of your indicators, and the lines, labels, tables and boxes your Pine scripts draw. They can also change the chart, draw on it, manage price alerts, write and compile Pine Script, step through replay and take screenshots. It needs TradingView Desktop (the README says real-time data takes a paid subscription), Node.js 18 or later and Claude Code. It does not place trades. Our guide to Claude Code for trading covers the safer, broker-connected side of running Claude Code near real money.
The setup, in short: clone the repository, run npm install, add the server to Claude Code’s MCP config, start TradingView with --remote-debugging-port=9222, and ask Claude to run its health check tool. The README is candid about the trade-off. The tool “accesses undocumented internal TradingView APIs” that “can change or break without notice,” its use “may conflict with” TradingView’s Terms, and you “assume all risk,” while the authors take no responsibility for account bans. Forks such as LewisWJackson/tradingview-mcp-jackson, the “Jackson” version that comes up in searches, add a morning brief built on a rules file of your own on top of the same bridge.
Good prompts name the data source, ask for the time of the data and keep what TradingView returned apart from what Claude worked out. Three to start with, for the official server:
Using the TradingView connector only, get the technical ratings for NASDAQ:NVDA on the 1D, 4h, 1h and 15m timeframes. For each one, give the trend, RSI and MACD in one line. Then pull 300 daily bars and list the two nearest support and resistance levels, with the dates price touched them. Tell me the time of the last bar you received, and mark which numbers came from TradingView and which you calculated.
Run TradingView’s screener on S&P 500 stocks with RSI under 40 and revenue growth above 10%. Show the 10 with the highest volume in a table with price, RSI and P/E. Then propose a watchlist called “RSI dips” with them, and wait for my OK before you create anything.
Which stocks on my TradingView watchlist report earnings in the next 10 days? For each one, give the date, the consensus EPS and revenue, and how revenue grew over the last four quarters. Use only the TradingView tools and tell me if any data is missing.
Two requests won’t work yet: an alert on an indicator, which the docs say is rejected for now, and “look at my chart,” since the server can’t see it. Ask for a price alert instead, or use a route that reads the chart.
TradingView’s Terms of Use have a section for the MCP server, section 27. The points that matter most:
Behind all of this sits section 3, the base rule for every piece of TradingView data: it is licensed “for exclusive display-only use,” which excludes “any form of automated trading.” For community tools, section 12 is the one to read. Without TradingView’s written consent, it rules out automated means of extracting data from TradingView, “including by accessing or querying internal or undocumented endpoints,” unless you go through “official TradingView APIs or other interfaces that we expressly make available for that purpose.” The official MCP server is such an interface. A bridge built on undocumented internals is the case its own README warns you about.
It runs on TradingView’s side, you sign in on TradingView’s page, and you can cut it off from Claude or from TradingView.
It runs with your permissions. Read the README and, if you can, the code, and install from the original repository rather than a copy.
The atilaahmettaner README says copies published under other accounts add npm dependencies that install malware, and that anyone who ran npm install on such a copy should treat the machine as compromised.
A key written into Claude Desktop’s config file sits there as plain text. Use free or read-only keys where you can, and never a key that can move money.
Leave approvals on for write tools. Anthropic’s advice is to “only click ‘Allow always’ when using a server and tool that you trust to run unsupervised.”
News stories and filings are written by others. Anthropic warns that malicious MCP servers “may include hidden instructions,” so read untrusted content in a session that can’t act on your accounts.
Yes. Ethy, an AI trading agent, reads the chart on four timeframes without a connector, a config file or a TradingView login. Ask about a market and it reads the daily, 4-hour, 1-hour and 15-minute charts together: the trend on each, support and resistance, RSI and MACD divergences, Fibonacci levels, VWAP, volume nodes, patterns and an overall bias. There is no broker to connect and nothing to install.
It also covers two things the TradingView server doesn’t offer today. It sets indicator alerts, on an RSI level, a 9/21 EMA cross or a MACD cross, and sends them to the app or to Telegram. And it backtests a rule you describe in plain words on up to a year of history, with every entry and exit marked on the chart. When you want to know why a market moved, it runs a web search and cites what it found.
To be clear about the link with TradingView: Ethy’s charts are drawn with TradingView’s charting library, fed with Ethy’s own market data. Ethy doesn’t connect to your TradingView account, import your Pine scripts or take in TradingView alerts. If you are also wondering whether an AI can place the trade, start with can Claude trade for you: it covers Claude with a broker, the risks, and where an agent like Ethy fits. Ethy vs Claude compares the two job by job.
Yes. TradingView opened its MCP server in public beta on September 16, 2026, at mcp.tradingview.com/mcp. It works in Claude on the web, desktop and mobile, in Claude Code, and in other MCP clients. You sign in with your TradingView account, with no API key. It needs an Essential plan or higher; trial plans are excluded.
Not through the official MCP server, which has no tool for your layout, drawings or Pine scripts. TradingView’s AI Copilot, a paid add-on inside its charts, does see your chart, and since November 9, 2026 you can choose Claude Sonnet 5.5 as its model. Community bridges that drive TradingView Desktop can read your chart too, at your own risk under TradingView’s Terms.
Not in the beta. TradingView says market data through the server is delayed, and its Terms add that some data may be delayed, limited or unavailable because of data provider rules. Before you rely on a number, ask Claude for the time of the last bar it received and compare it with your chart.
No. The official server has no order tools, and TradingView’s Terms forbid having an AI client place, modify or cancel orders with any broker using its data, or wiring its alerts to a bot that trades. Placing orders takes a broker connector, which is a separate question with its own risks.
Yes. TradingView’s docs give setup steps for ChatGPT and Codex, Grok, Perplexity and Cursor, plus any client that supports MCP over streamable HTTP with OAuth 2.1 sign-in. The same server URL works in all of them.
It usually means LewisWJackson/tradingview-mcp-jackson on GitHub, a fork of tradesdontlie/tradingview-mcp. It connects Claude Code to TradingView Desktop through the Chrome DevTools Protocol and adds a morning brief built on your own rules file. TradingView doesn’t make it and it relies on undocumented internals. Its MCP tools don’t place trades, but the repository also ships a separate script that places orders on Bitget with your API keys: read it before you run anything.
Trading involves risk, including the loss of your money. Ethy AI is a research and trading tool and does not give investment advice or recommendations. Backtests are simulations on historical data and do not predict future results.
Deploy your AI trading agent in one click.
