How to Connect Claude AI to TradingView Using MCP

TradingView doesn’t ship an official way to plug Claude AI into your charts.

What exists instead is a small, fast-moving set of community-built MCP servers, and this guide walks through installing one. It’s the general setup path: stocks, crypto, forex, and futures all work the same way once the config is in place.

You’ll learn what Model Context Protocol (MCP) actually does, which TradingView MCP servers are real and maintained versus abandoned side projects, and the exact Claude Desktop config steps to wire one up. We’ll also cover where this setup stops. Trading futures on a funded or prop-firm account? Our futures-specific Claude + MCP guide goes deeper on execution risk and walks through a live funded-account example.

Key Takeaways

• No official TradingView MCP server exists from Anthropic or TradingView. Every option is third-party, and reliability ranges from 5,750 GitHub stars down to under 25.
• Claude connects to MCP servers through a JSON config file, not an app-store install. Claude Desktop uses claude_desktop_config.json; Claude Code uses .mcp.json.
• MCP lets Claude read charts, indicators, and Pine Script. It doesn’t place broker orders on its own. That step still runs through TradingView’s native webhook alert.
• Works the same across asset classes: the config is identical whether you’re checking a stock RSI, a crypto chart, or an FX pair.

What does MCP actually let Claude do with TradingView?

Model Context Protocol is Anthropic’s open standard for connecting Claude to outside tools and data. Every action requires your explicit approval before it runs. An MCP server is a small program on your machine that translates Claude’s requests into calls a specific tool understands, in this case, TradingView data.

Is that the same as an official TradingView integration? No. Anthropic has since handed governance of the MCP specification itself to an independent foundation backed by OpenAI, Google, Microsoft, and Amazon, which standardized the protocol, not any particular server built on top of it. TradingView hasn’t published one.

Worth noting: every TradingView MCP server we found pulls data through public endpoints, scraping, or a locally logged-in desktop app, never through an official TradingView API partnership. That’s the gap between “Claude can read your charts” and “this is a supported integration,” and it shapes every setup decision below.

With a server installed, Claude can typically pull real-time quotes, compute indicators like RSI or MACD, read or draft Pine Script, and summarize what a chart is showing you in plain language. It works the same whether you’re looking at a tech stock, a Bitcoin pair, or a Micro E-mini futures contract.

What it can’t do, for any server we found, is place a trade on your broker directly.

For background on TradingView’s own alert system before you start, see PickMyTrade’s guide to TradingView’s custom alert tools. That’s the mechanism your MCP-assisted analysis eventually feeds into.

Which TradingView MCP server fits your setup?

Four community projects currently claim TradingView support on GitHub, and star counts alone don’t tell you which one to pick. The right choice depends on whether you need live chart and drawing access or just clean market data without logging into anything.

Here’s what separates them in practice:

• tradesdontlie/tradingview-mcp bridges Claude Code to a locally running TradingView Desktop app through Chrome DevTools Protocol, giving Claude access to live drawing tools and Pine Script editing. It requires an active TradingView subscription and uses undocumented internal interfaces the maintainer flags as liable to break.
• atilaahmettaner/tradingview-mcp pulls public market data for stocks, crypto, forex, and futures, with 37 technical-analysis tools and a built-in backtester. No TradingView login is required. Install via pip install tradingview-mcp-server.
• The smaller projects (fiale-plus, bidouilles) work but carry real risk. Low star counts mean fewer eyes have caught bugs, and one labels itself “for educational and research purposes” only.

Don’t pick the biggest number blindly. Pick based on what you’re actually trying to do. Do you need Claude looking at your live TradingView session with drawing tools, or just the numbers behind it? For most setups across stocks, crypto, and forex, the data-only route is the simpler starting point.

What do you need before you start?

You’ll need Claude Desktop or Claude Code installed, Node.js 18+ or Python 3.11+ depending on which server you pick, and about 15 to 20 minutes. If you’re going with the Desktop-bridge server, you also need an active TradingView subscription and the desktop app running locally.

You’ll need:

• Claude Desktop or Claude Code, latest version
• Node.js 18+ (for npm-based servers) or Python 3.11+ with pip/uv (for Python-based servers)
• A TradingView account. Free tier covers the data-only servers; a paid subscription is required for the Desktop-bridge server
• Basic comfort editing a JSON file in a text editor
• ~15 to 20 minutes

How do you configure Claude for MCP?

Claude reads MCP server definitions from a single JSON file that you edit once per server you add. Claude Desktop and Claude Code use different files, and editing the wrong one is the single most common reason a setup does nothing. On macOS, Claude Desktop’s config lives at ~/Library/Application Support/Claude/claude_desktop_config.json. On Windows, it’s at %APPDATA%\Claude\claude_desktop_config.json. Claude Code instead reads a .mcp.json file in your project directory, which matters if you’re already running Claude Code inside a repo that has its own strategy scripts, since the server then applies only to that project rather than globally.

Step 1: open the config file

For Claude Desktop, open the Claude menu (not the in-app Settings panel), then Settings, then the Developer tab, then Edit Config. This creates the file automatically if it doesn’t exist yet. For Claude Code, create or open .mcp.json in your project root.

Step 2: add the server entry

Paste your server’s entry into the mcpServers object. Here’s the general pattern:

{
  "mcpServers": {
    "tradingview": {
      "command": "uvx",
      "args": [
        "--from",
        "tradingview-mcp-server",
        "tradingview-mcp"
      ]
    }
  }
}

On Windows, use double backslashes in any file paths inside the config, like "C:\\Users\\yourname\\...". Substitute the exact command and args your chosen server’s README specifies: npx -y for npm-based servers, uvx --from for Python ones.

Step 3: restart fully

Quit the app completely. Closing the window isn’t enough. Relaunch it, and your new server should appear under the connectors icon at the bottom-left of the chat box, then Manage connectors.

Verify your setup: open a new chat and ask something concrete, like “What’s the current RSI on AAPL?” or “Pull the latest price for BTC/USD.” If the server connected correctly, Claude will prompt you to approve the tool call before it runs.

What we found installing this: the most common snag isn’t the JSON syntax. It’s forgetting the full quit-and-relaunch step. A simple window close leaves the old config cached, and the new server just never shows up in the connectors list.

Common setup errors:

How do you use Claude and MCP to analyze charts across asset classes?

Once connected, ask Claude to pull an indicator reading, summarize price action, or draft a Pine Script alert condition. It calls the MCP server behind the scenes to fetch real data instead of guessing. That’s the actual point of the setup: grounding Claude’s answers in your current chart, not stale training data.

A typical workflow spans asset classes without changing your setup at all. Ask Claude whether a tech stock is above its 20-day moving average. Have it explain what a Pine Script condition does line by line on a crypto chart. Ask it to draft a JSON alert payload template for an FX pair that you can paste straight into a TradingView alert. The prompts change; the underlying MCP connection doesn’t.

None of this touches your broker account. Every server we reviewed stops at reading and analyzing. It doesn’t submit orders. That boundary is deliberate on the maintainers’ part, and it’s also exactly where TradingView’s own alert system picks up.

How does this fit into full trade automation?

Claude with MCP helps you read a chart and refine a Pine Script alert condition, but the order still has to reach your broker through TradingView’s own alert system. When a TradingView alert fires, it sends an HTTP request to whatever webhook URL you’ve configured. See PickMyTrade’s webhook automation guide for the exact payload format and timing requirements.

That webhook is exactly what PickMyTrade listens on. It parses the incoming JSON payload and routes the order to your connected broker or prop-firm account across stocks, futures, and crypto. See the TradingView automation page for full broker and prop-firm coverage. Put plainly: Claude plus MCP is the analysis layer, TradingView’s alert system is the trigger, and PickMyTrade is the execution layer, and each piece does one job well instead of one tool trying to do all three. If you’re trading futures on a funded account specifically, our futures-focused Claude + MCP walkthrough covers position sizing against drawdown limits and prop-firm compliance rules in detail.

Is it safe to connect an AI assistant to your trading setup?

Yes, with caveats specific to this being unofficial software.

Every MCP server here is community-maintained, not published or endorsed by TradingView, and a couple rely on undocumented internal APIs the maintainers themselves warn “may change or break at any time.” Treat install stability as your own risk, and re-check the repo before every update. Stick to data-only servers like atilaahmettaner’s if you’d rather not log a desktop app into your live TradingView session at all, since it pulls public data and needs no account. Claude also asks for per-action approval before any MCP tool call runs, so nothing executes silently in the background.

On the webhook side, never put account credentials or passwords inside a webhook alert message body. Keep that boundary intact whether Claude drafted the payload template or you wrote it by hand.

What should you do next?

Start with the smallest useful setup: install a data-only MCP server, confirm Claude can read a live quote, then layer in Pine Script drafting once that’s stable. If your goal is full automation rather than just analysis, connect your existing TradingView webhook alert to PickMyTrade so the strategies Claude helps you refine actually reach your broker.

Trading futures on a prop-firm or funded account? Skip ahead to our Claude AI futures trading guide for the execution-risk deep dive, including a walkthrough on a funded Apex account. For deeper background on alerts generally, see TradingView’s custom alert tools guide. Questions about broker or prop-firm compatibility can go to the team via PickMyTrade’s contact page, or read more about the team behind the webhook pipeline.

Frequently asked questions

Conclusion

Connecting Claude to TradingView through MCP works. Just go in knowing it’s community software, not an official product, and that it stops well short of touching your broker account. Pick a server that matches your risk tolerance, get the JSON config right the first time, and verify with a simple quote request before you build anything more complex.

From there, the path to full automation runs through TradingView’s own webhook alerts and a dedicated execution layer. See how PickMyTrade routes TradingView alerts to your broker or prop-firm account, or go straight to the futures-specific execution walkthrough if that’s your asset class.

Disclaimer:
This content is for informational purposes only and does not constitute financial, investment, or trading advice. Trading and investing in financial markets involve risk, and it is possible to lose some or all of your capital. Always perform your own research and consult with a licensed financial advisor before making any trading decisions. The mention of any proprietary trading firms, brokers, does not constitute an endorsement or partnership. Ensure you understand all terms, conditions, and compliance requirements of the firms and platforms you use.

Also Checkout: The Wash Sale Rule Trading Bots Keep Triggering by Accident