Claude · TradingView Official MCP Server · AI Research · 2026
Claude can now connect directly to TradingView through TradingView’s official MCP Server. This is a major change from earlier 2026, when connecting Claude to TradingView usually meant relying on an unofficial local bridge.
TradingView launched its official MCP Server in public beta in September 2026. The connection works with Claude on the web, desktop, mobile, and Claude Code, uses TradingView account authorization instead of a custom API key, and is currently included with Essential, Plus, Premium, and Ultimate. TradingView’s current MCP documentation says trial plans do not include MCP access.
Once connected, Claude can use TradingView data and tools for market research, screening, fundamentals, news, filings, calendars, watchlists, alerts, and data-driven coding workflows. This guide shows the current official setup, what Claude can actually do, where the beta limits begin, and when TradingView AI Copilot may be the better tool.
Important update: this guide previously covered an independent TradingView MCP Bridge that required TradingView Desktop and local debugging access. TradingView now provides an official remote MCP Server, so that third-party route is no longer the default setup we recommend.
Key Takeaways
- TradingView now has an official MCP Server. You no longer need the old third-party local bridge for the normal Claude connection.
- Claude web, desktop, mobile, and Claude Code are supported. The normal Claude setup uses a custom connector; Claude Code uses the official MCP URL over HTTP.
- MCP access begins at TradingView Essential. Plus, Premium, and Ultimate are also eligible. TradingView’s current MCP docs say trial plans do not include MCP access.
- No TradingView API key is required. The official server uses TradingView account authorization via OAuth.
- The MCP Server is best for external AI research and data workflows. It can pull quotes and history, run screeners, use fundamentals/news/filings/calendars, and manage supported watchlist and alert workflows.
- AI Copilot and MCP are different products. AI Copilot lives inside Supercharts and can act directly on the chart; MCP brings TradingView data and supported tools into Claude and other AI clients.
- The MCP Server is still in public beta. TradingView says the tool set is scoped, market data can be delayed, request limits may apply, and some tools may not always work smoothly.
Table of Contents
- Can Claude Connect to TradingView?
- What Changed in September 2026?
- What You Need
- How to Connect Claude to TradingView
- How to Connect Claude Code
- How to Verify the Connection
- What Can Claude Do with TradingView MCP?
- Best Claude + TradingView MCP Prompts
- TradingView AI Copilot vs Claude + MCP
- Which TradingView Plan Do You Need?
- Current MCP Beta Limitations
- Security and Privacy
- What About the Old Third-Party MCP Bridge?
- A Better Claude + TradingView Workflow
- Troubleshooting
- FAQ
Can Claude Connect to TradingView?
Yes. TradingView now provides an official MCP Server designed specifically to connect TradingView data and supported platform tools to MCP-compatible AI clients such as Claude.
The official server URL is:
https://mcp.tradingview.com/mcpFor the normal Claude experience, you add that URL as a custom connector, authorize access with your TradingView account, and then Claude can call the supported TradingView tools from the conversation.
Claude → Official TradingView MCP Server → TradingView data & supported account tools
This is much cleaner than the earlier local-bridge setup because you do not need to launch TradingView Desktop with a debugging port, install a third-party Node project, or expose an authenticated desktop session to local automation software.
What Changed in September 2026?
TradingView launched its own MCP Server as a public beta on September 16, 2026. That fundamentally changed the answer to “How do I connect Claude to TradingView?”
| Earlier 2026 | Current Official Route |
|---|---|
| Use an independent local TradingView MCP bridge. | Use TradingView’s official remote MCP Server. |
| Requires TradingView Desktop. | Does not require TradingView Desktop for the MCP connection. |
| Requires a local Node project and MCP configuration. | Paste one official server URL into a supported MCP client. |
| Often requires Chrome DevTools Protocol and a local debug port. | Uses TradingView account authorization with OAuth. |
| Depends on undocumented TradingView Desktop internals. | Officially maintained by TradingView during the public beta. |
| Primary strength: experimental local chart automation. | Primary strength: official TradingView data, research, screening, watchlists, alerts, and coding workflows inside AI clients. |
This does not mean the two systems expose exactly the same capabilities. The official server should be judged on the tools TradingView actually documents, while the older third-party bridge attempted deeper local Desktop control through undocumented interfaces.
What You Need Before Connecting Claude to TradingView
| Requirement | Current Rule |
|---|---|
| TradingView account | You authorize the official MCP Server with your TradingView account. |
| TradingView plan | Essential, Plus, Premium, or Ultimate. |
| Trial plan | TradingView’s current MCP docs say trials do not include MCP access. |
| Claude client | Claude web, desktop, mobile, or Claude Code can use the TradingView MCP connection. |
| TradingView Desktop | Not required for the official MCP Server connection. |
| API key | Not required. Authentication uses TradingView account authorization. |
| Node.js / Git / debug port | Not required for the normal official MCP setup. |
If you are on Basic / Free, MCP is therefore a plan-access decision first. Use our TradingView Free Plan guide if you are still deciding whether a paid plan is justified.
How to Connect Claude to TradingView with the Official MCP Server
For Claude on the web, desktop app, or mobile app, TradingView’s current setup is straightforward.
- Open Claude.
- Go to Settings → Connectors.
- Choose Add custom connector.
- Paste the official TradingView MCP URL:
https://mcp.tradingview.com/mcp- Add the connector.
- Sign in to your TradingView account when prompted.
- Review the authorization request and approve access.
- Start a new conversation and ask Claude to use TradingView.
Useful detail: TradingView says a connector added to Claude works across the Claude web, desktop, and mobile experiences associated with that setup, so you do not need a separate local TradingView Desktop bridge for each device.
A simple first prompt is:
Use TradingView data to give me a concise overview of AAPL: current price context, recent performance, key technical indicators, the latest major news, analyst consensus, and the next earnings date. Tell me which TradingView tools you used.How to Connect Claude Code to TradingView
Claude Code can use the same official TradingView MCP Server without the old local bridge.
TradingView currently documents this command:
claude mcp add --transport http mcp-tradingview https://mcp.tradingview.com/mcpThen open Claude Code and run:
/mcpAuthorize the TradingView connection in your browser when prompted. Once authorization succeeds, Claude Code can use the TradingView MCP tools available to your account.
Why Claude Code is interesting: the official MCP connection can turn TradingView into a data source for analysis scripts. TradingView specifically highlights workflows where Claude Code pulls price history and macro data, then writes and runs the analysis without manual CSV exports.
How to Verify the TradingView MCP Connection
Do not begin with a complex screening or alert workflow. First confirm that Claude can call TradingView successfully.
Try: Use the TradingView connector to get the current quote and recent daily price history for NVDA. Tell me whether the TradingView connection succeeded and identify any limitation or delay in the data you received.
If Claude cannot access TradingView, check the connector authorization, your TradingView plan, and whether you are currently using a trial rather than an eligible paid subscription.
What Can Claude Do with the Official TradingView MCP Server?
TradingView’s public beta is designed around market data, research, screening, account workflows, and AI-assisted analysis outside the TradingView chart interface.
| Workflow | Examples |
|---|---|
| Quotes and price history | Pull current market context and historical bars for supported symbols. |
| Technical analysis | Combine price action with available technical-indicator data. |
| Screening | Run TradingView Screener queries from natural-language criteria. |
| Fundamental research | Use financial data, analyst expectations, and company metrics. |
| News and events | Research headlines, earnings calendars, economic calendars, and supported filings. |
| Watchlists | Create or manage supported watchlist workflows from the conversation. |
| Alerts | Create and review supported TradingView alert workflows. |
| Comparison | Compare several stocks, cryptocurrencies, sectors, or other supported instruments in one structured response. |
| Coding and analysis | Use TradingView data inside Claude Code for scripts, calculations, and research workflows. |
One important boundary: the official MCP Server is not the same thing as AI Copilot inside Supercharts. Do not assume every chart-side Copilot action — such as changing layouts, drawing levels, or writing directly into Pine on the chart — is automatically exposed through MCP unless TradingView documents the relevant MCP tool.
Best Claude + TradingView MCP Prompts
The strongest MCP prompts use TradingView as a structured data and tools layer instead of asking Claude for a vague market opinion.
| Goal | Prompt to Try |
|---|---|
| Market briefing | Use TradingView to summarize NVDA’s recent price action, technical picture, latest major headlines, analyst consensus, and next earnings date. Separate facts from interpretation. |
| Value screen | Use TradingView Screener to find S&P 500 stocks with P/E below 15, positive revenue growth, dividend yield above 2%, and RSI below 40. Explain in one sentence why each currently looks weak. |
| Watchlist workflow | Find 15 large-cap US stocks with positive revenue growth and above-average dividend yield. Create a TradingView watchlist called “Income research” if the connector supports it, then summarize the result. |
| Alert review | Check which of my supported TradingView alerts fired recently. For each, summarize the price move afterward and the most relevant news context you can verify. |
| Earnings prep | Find companies in my watchlist reporting earnings in the next 10 days. Show expected EPS, revenue expectations, recent revenue growth, and the stock’s reaction to the previous four reports. |
| Cross-asset comparison | Compare BTC, ETH, and SOL over the last 90 days using TradingView data: return, max drawdown, volatility, and current technical momentum. Put the results in one table. |
| Research challenge | Use TradingView data to build the strongest bullish and bearish case for this company. List the evidence for each and identify what data would invalidate each thesis. |
| Claude Code analysis | Pull two years of daily BTCUSDT history and a relevant macro series from TradingView, calculate a rolling 90-day relationship, and write a reproducible script that plots the result. |
Prompt quality rule: tell Claude what should come from TradingView, what should be calculated, what should be interpreted, and what uncertainty should remain visible.
TradingView AI Copilot vs Claude + Official MCP Server
These tools now make much more sense when treated as complementary rather than competing versions of the same product.
| Feature | TradingView AI Copilot | Claude + TradingView MCP |
|---|---|---|
| Where it lives | Inside TradingView Supercharts | Inside Claude / Claude Code |
| Main strength | Chart-aware analysis and actions without leaving TradingView | External research, screening, data, watchlists, alerts, and AI workflows using TradingView as the data/tool layer |
| TradingView plan | Paid plan required, then Copilot is purchased as a separate add-on | Included with Essential, Plus, Premium, and Ultimate during the current beta |
| Trial access | TradingView currently allows the Copilot add-on flow from eligible paid-plan trials | TradingView’s current MCP docs say trials do not include MCP access |
| Mobile | Not yet available in TradingView mobile apps | TradingView says the MCP connector works with Claude mobile |
| Chart actions | Can switch symbols/layouts, add indicators, draw levels, create alerts/watchlists, and write/apply Pine | Use only the MCP tools TradingView currently exposes; do not assume full Supercharts control |
| Best fit | Users who want AI directly beside the chart | Users who want TradingView data and account tools inside Claude or coding/research workflows |
For the chart-side workflow, read our updated TradingView AI Copilot guide.
Which TradingView Plan Do You Need for MCP?
TradingView currently includes the MCP Server in Essential, Plus, Premium, and Ultimate. Basic / Free does not include MCP access, and TradingView’s current MCP documentation says trial plans do not include it either.
That means Essential is the lowest standard paid tier that qualifies for the official MCP Server. You do not need Plus, Premium, or Ultimate purely to unlock MCP.
Do not choose the whole TradingView plan around MCP alone. Pick the plan based on the chart, indicator, alert, history, connection, and workflow limits you actually need. MCP access is then an additional benefit of any eligible paid tier.
Current TradingView MCP Beta Limitations
The official route is much cleaner than the old third-party setup, but “official” does not mean “finished.” TradingView explicitly labels the MCP Server a public beta.
- The tool list is still scoped. Not every TradingView feature is available through MCP.
- Market data can be delayed. Do not assume every MCP result is a tick-for-tick real-time feed.
- Request limits may apply. TradingView says it may limit the number of daily requests during the beta to keep the service reliable.
- Some tools may fail or behave imperfectly. Beta workflows can change as TradingView expands the server.
- Your normal account entitlements still matter. MCP does not magically unlock exchange data or paid features outside your account access.
- AI interpretation can still be wrong. Official TradingView data improves grounding, but Claude can still make reasoning mistakes.
Good beta workflow: use MCP for research and automation that you can verify. Do not build a mission-critical process around an undocumented assumption about a beta tool.
Security and Privacy: What Changes with the Official Server?
The official MCP setup removes several risks that came with the earlier local bridge. You no longer need to open a TradingView Desktop debug port or install third-party code just to make the normal connection.
- Authorization uses your TradingView account. TradingView documents OAuth-based authorization instead of a personal TradingView API key.
- Review the requested permissions before approving access.
- Use the official MCP URL. Verify that the server address is
https://mcp.tradingview.com/mcp. - Do not paste passwords, broker credentials, private keys, or unrelated sensitive data into prompts.
- Keep AI actions reviewable. If Claude creates a watchlist or alert, verify the result in TradingView.
What About the Old Third-Party TradingView MCP Bridge?
This article originally documented an independent bridge that connected Claude Code to TradingView Desktop through Chrome DevTools Protocol. That setup was useful when TradingView did not yet provide its own MCP Server.
It may still interest advanced users who specifically want experimental local Desktop automation that the official server does not expose. However, it has important tradeoffs: third-party code, local debug access, dependency on undocumented TradingView Desktop internals, and a greater chance of breaking after application updates.
Our current recommendation: start with TradingView’s official MCP Server. Only evaluate third-party local bridges if you can clearly name a capability you need that the official server does not provide and you are comfortable reviewing and maintaining the additional security and technical complexity.
A Better Claude + TradingView Workflow
| Step | Action | Why |
|---|---|---|
| 1 | Confirm the official connector is authorized | Avoid troubleshooting prompt quality when the real problem is access |
| 2 | Ask for a simple quote/history request | Verify TradingView tools are working |
| 3 | Ask Claude to identify which data came from TradingView | Separate source data from AI interpretation |
| 4 | Use specific screening or research criteria | Make the output reproducible |
| 5 | Ask for both supporting and contradictory evidence | Reduce one-sided AI summaries |
| 6 | Review watchlist and alert changes in TradingView | Keep account actions understandable |
| 7 | Use Claude Code only when coding adds real value | Avoid unnecessary technical complexity |
| 8 | Keep investment and trading decisions human-controlled | AI research is not guaranteed market judgment |
The real advantage of MCP is not that Claude becomes a “trader.” It is that you can use TradingView as a structured market-data and tools layer inside an AI workflow, reducing manual copying and repetitive research.
Want TradingView Inside Claude?
Official MCP access currently starts with Essential. Compare the paid tiers around your normal TradingView needs first — then treat MCP as an extra workflow benefit.
Troubleshooting Claude + TradingView MCP
| Problem | What to Check |
|---|---|
| Claude cannot see the TradingView connector | Confirm the custom connector was saved and that your Claude client supports MCP connectors. |
| TradingView authorization fails | Sign in to the correct TradingView account and re-check the authorization flow. |
| Connector is added but TradingView tools do not work | Verify that your TradingView account is on Essential or above and is not only on a trial. |
| Claude returns no current market data | Remember that the MCP beta may return delayed data and has a scoped tool set. |
| Claude Code cannot connect | Run /mcp, confirm the TradingView server entry, and complete browser authorization. |
| A tool worked before but fails now | TradingView’s MCP Server is still a beta; check the current official MCP documentation for tool or access changes. |
FAQ: Claude and TradingView MCP
Can Claude connect to TradingView?
Yes. TradingView now provides an official MCP Server that works with Claude web, desktop, mobile, and Claude Code.
Is the Claude + TradingView connection official now?
Yes. TradingView launched its own official MCP Server in public beta in September 2026. This guide now uses that official connection as the default method.
What is the official TradingView MCP Server URL?
The current official URL is https://mcp.tradingview.com/mcp. Verify the address before authorizing your TradingView account.
Do I need TradingView Desktop to connect Claude?
No. TradingView Desktop was part of the older third-party bridge workflow. The official TradingView MCP Server is a remote connection and does not require the Desktop app for normal MCP access.
Which TradingView plans include MCP?
TradingView currently includes MCP access with Essential, Plus, Premium, and Ultimate.
Does TradingView Free include MCP?
No. Basic / Free does not currently include TradingView MCP access.
Can I use TradingView MCP during a free trial?
TradingView’s current MCP documentation says trial plans do not include MCP access.
Does Claude mobile work with TradingView MCP?
TradingView says its official MCP Server works with Claude web, desktop, mobile, and Claude Code.
Do I need a TradingView API key?
No. TradingView’s official MCP Server uses TradingView account authorization rather than requiring you to manage a separate API key.
Can Claude use TradingView Screener?
Yes. TradingView explicitly lists Screener workflows among the official MCP Server use cases.
Can Claude manage TradingView watchlists and alerts?
TradingView lists supported watchlist and alert workflows among the current MCP Server capabilities. Because the server is still in beta, verify the exact tools available to your account.
Can Claude control my active TradingView chart through MCP?
Do not assume full Supercharts control. TradingView’s AI Copilot is the product designed for direct chart-side actions. The official MCP Server exposes a scoped set of data and account tools that TradingView is expanding during the beta.
What happened to the old TradingView MCP Bridge?
The independent local bridge still exists as a separate experimental project, but TradingView now offers an official MCP Server. For most users, the official server is the better starting point because it avoids local debug ports and third-party Desktop automation.
Is TradingView MCP better than AI Copilot?
They solve different problems. AI Copilot works directly inside TradingView charts. MCP brings TradingView data and supported tools into Claude and other AI clients. Choose based on where you want the AI workflow to live.
Related TradingView Guides
About ChartWiseHub
ChartWiseHub helps traders and investors understand TradingView through practical tutorials, current product guides, troubleshooting resources, and decision tools. We update fast-changing TradingView AI and plan content when the underlying products change, rather than leaving old setup instructions live after the platform moves on.
Transparency & Risk
ChartWiseHub is reader-supported and this article contains affiliate links. Read our Affiliate Disclosure, Financial Disclaimer, and Editorial Standards.