pueschel88/tradingview-mcp — explained in plain English
Analysis updated 2026-05-18
Let an AI assistant read the current symbol, timeframe, and price from your open TradingView chart.
Ask an AI assistant to switch the chart's symbol or timeframe during a conversation.
Pull recent OHLCV price bars from the active chart for an AI to analyze.
| pueschel88/tradingview-mcp | stormeye85/robinhood-token-sniper | boob025/peace-equalizer-apo | |
|---|---|---|---|
| Stars | 133 | 133 | 134 |
| Language | TypeScript | TypeScript | TypeScript |
| Setup difficulty | — | — | easy |
| Complexity | 3/5 | 3/5 | 1/5 |
| Audience | developer | developer | general |
Figures from each repo's GitHub metadata at analysis time.
Tradingview MCP is a small server that lets Claude Code, or any other MCP-compatible AI assistant, control a TradingView Desktop application that is already running on your computer. MCP stands for Model Context Protocol, a standard way for AI tools to call external tools. Instead of scraping TradingView's website or getting around any paywall, this project connects to the desktop app you already log into and pay for, using the Chrome DevTools Protocol, the same debugging interface built into Electron apps like Slack, VS Code, and Discord. Once connected, an AI assistant can read the current chart, including the symbol, timeframe, visible indicators, and last price, and it can change the symbol or timeframe on your behalf. It can also fetch up to 5,000 recent OHLCV bars, meaning open, high, low, close, and volume price data, directly from the active chart. All of this happens locally: no chart data is sent anywhere else or stored by the tool itself. The project deliberately keeps its feature set small, with a handful of well defined, typed tools rather than a large kitchen sink set of features. It includes a doctor command that checks whether the connection to TradingView Desktop is working and reports what is wrong if it is not. Setup involves quitting TradingView Desktop, relaunching it with a debug port flag enabled, and then adding the tool to your Claude Code configuration. An optional local Redis cache can be used to reduce repeated calls to the chart, and the tool still works without Redis running, just without that caching benefit. The code is written in TypeScript with strict type checking, split into separate layers for the connection, the chart tools, and the server itself, and it ships with tests. This is aimed at developers who already use TradingView Desktop and want an AI assistant to read chart state or pull price data as part of a workflow, such as asking an assistant to switch symbols or summarize recent price movement. It is not affiliated with TradingView Inc. and requires an existing TradingView subscription and a locally running desktop app to work.
A local MCP server that lets Claude Code or another AI assistant read and control your running TradingView Desktop chart.
Mainly TypeScript. The stack also includes TypeScript, Zod, Chrome DevTools Protocol.
The README does not state a license, so usage rights are unclear.
Mainly developer.
This repo across BitVibe Labs
Don't trust strangers blindly. Verify against the repo.