TradingView launches an official MCP server: what it means for algo traders

TradingView has released an official MCP server, so AI assistants such as Claude, ChatGPT, Grok and Perplexity can now connect directly to a TradingView account. It went into public beta on 16 September 2026 for Essential plans and above. Six weeks in, plenty of guides online still say no official server exists, so here's a short summary of what changed and what it means if you trade a systematic strategy.

What launched

The server lives at https://mcp.tradingview.com/mcp. You add it as a custom connector in your assistant and sign in with your TradingView account, with no API key. According to TradingView's documentation, it gives the assistant 35 tools:

• Price history (up to 5,000 bars per request), symbol search and economic data
• The screener, technical ratings and screener columns for up to 50 symbols at once
• News, fundamentals, analyst forecasts, filings and earnings call transcripts
• Earnings, dividend and economic calendars
• Your watchlists and simple price alerts, which it can create, change and delete

Market data is delayed during the beta, tool calls are limited to about 100 a minute, and it can't place trades.

What it doesn't do

None of the 35 tools read or write Pine Script, and none return Strategy Tester results. The assistant can tell you what the market did, but it can't see what your strategy did.

That matters more than it sounds. The questions a systematic trader actually needs answered after a backtest are about the strategy's own trades: which sessions lose money, whether Mondays drag the results down, whether the stop is too tight in high volatility. An assistant connected to price data can't answer those, because the answers aren't in price data. They're in your trade list.

Community projects fill part of the gap. The most popular one drives TradingView Desktop through a debugging port, so Claude Code can write, compile and run Pine Script and read Strategy Tester data. Its own README warns that it relies on undocumented internal TradingView APIs, so treat it as a power-user tool rather than a supported one.

How we'd use it

For algo traders, the official server is best as a research and monitoring assistant:

• A morning briefing on your watchlist before the session: news, earnings dates and economic events
• Screening in plain English for new markets to test a strategy on, saved straight to a watchlist
• Checking which price alerts fired overnight and what price did next

For strategy work, keep the two jobs separate. Use AI to write and refine the Pine Script, run it in the Strategy Tester with realistic costs, then export the trades and break them down by market condition before you trust the result.

Read more

We've written two in-depth guides to go with this:

• How to connect Claude to TradingView: step-by-step setup for Claude, Claude Code, ChatGPT and other assistants.
• TradingView MCP server: what it can and can't do: the official server compared with community bridges, tool by tool.

And if you're testing a strategy an AI helped you write, start with How to test a strategy ChatGPT or Claude wrote, or upload your Strategy Tester export for a free report on how it performs by session, weekday, time and volatility.