A focused, type-safe MCP server that lets Claude Code (or any MCP-compatible client) drive a locally-running application — read chart state, change symbols and timeframes, fetch OHLCV bars, capture screenshots.
Tradingview MCP server for controlling Tradingview Desktop from Claude Code via Chrome DevTools Protocol
स्टार
134
टूल
—
अपटाइम
—
TradingView Desktop
[!IMPORTANT]
This project is not affiliated with, endorsed by, or associated with TradingView Inc. It is a personal-use bridge that interacts with your locally running TradingView Desktop application via the Chrome DevTools Protocol — the same standard debug interface built into Slack, VS Code, Discord, and every other Electron app.
[!IMPORTANT]
Requires a valid TradingView subscription. This tool does not bypass, scrape, or circumvent any TradingView paywall or access control. Everything happens on your machine, against the TradingView Desktop instance you have already logged into and paid for.
[!NOTE]
All processing is local. No TradingView data is transmitted, stored, or redistributed by this tool. Your charts, your data, your machine.
[!CAUTION]
TradingView's internal page API is undocumented. It can change between Desktop releases. Pin a working TradingView Desktop version if you want stability, and check the version compatibility note before upgrading.
What it does
Wraps the TradingView Desktop chart in a small set of well-defined MCP tools. Tools are typed end-to-end with Zod schemas, validated at the boundary, and surface useful error messages when something goes wrong.
Existing TradingView automation projects exist. This one is deliberately scoped down:
12 tools, not 78. Every tool is documented, typed, and tested.
Strict TypeScript. No any, no implicit returns, noUncheckedIndexedAccess on.
One responsibility per file. Connection, page, tools, and server are separate layers — version drift only requires fixing one spot.
Typed errors.ConnectionError, ToolExecutionError, ChartStateError etc. with actionable messages.
tradingview-mcp doctor. A diagnostic command that tells you exactly what's wrong with your setup.
Use this if you want a small, predictable surface you can read in an afternoon. Use the kitchen-sink alternatives if you want every TradingView feature wrapped.
Install
For development:
git clone https://github.com/pueschel88/Tradingview-MCP.git
cd Tradingview-MCP
npm install
npm run build
Redis (optional, recommended)
Read tools (chart_get_state, quote_get, chart_get_ohlcv) are cached in a local Redis instance to reduce CDP round-trips. Redis is enabled by default and connects to 127.0.0.1:6379.
Windows (Docker):
docker run -d --name redis -p 6379:6379 redis:7-alpine
macOS (Homebrew):
brew install redis
brew services start redis
If Redis is not running, the server still works — it logs a warning and skips caching. Set TV_MCP_REDIS_ENABLED=false to disable Redis entirely.
Setup — three steps
1. Quit any running TradingView Desktop
Otherwise the debug port can't be enabled.
2. Launch TradingView Desktop with the debug port enabled
macOS:
open -a "TradingView" --args --remote-debugging-port=9222
[!NOTE]
The --remote-debugging-port flag is a standard Chromium debug flag. It is opt-in and disabled by default. Nothing happens without you explicitly passing it.
3. Verify the connection
tradingview-mcp doctor
If everything is wired up, you'll see something like:
tradingview-mcp · doctor
─────────────────────────────────────────────
[ok] CDP endpoint reachable on localhost:9222
[ok] TradingView page found (NASDAQ:AAPL · 1h)
[ok] tvWidget detected — chart state readable
─────────────────────────────────────────────
ready.
Use with Claude Code
Add this to your Claude Code MCP config (~/.claude/mcp.json or project .mcp.json):
You: What's the chart showing?
Claude: [calls chart_get_state]
Showing NASDAQ:AAPL on 1h timeframe with EMA20, EMA50.
Last price 187.42.
You: Switch to BTCUSDT 4h and pull the last 200 bars.
Claude: [calls chart_set_symbol, chart_set_timeframe, chart_get_ohlcv]
Done. Range: 187 days. Open at start: 62,440.
Close at end: 67,830. +8.6%.
Configuration
Env var
Default
Description
TV_MCP_HOST
localhost
CDP host
TV_MCP_PORT
9222
CDP debug port
TV_MCP_TARGET
(auto-detect)
Explicit CDP target ID — only needed if you have multiple TradingView windows open
TV_MCP_REDIS_ENABLED
true
Enable local Redis caching for read tools
TV_MCP_REDIS_HOST
127.0.0.1
Redis host
TV_MCP_REDIS_PORT
6379
Redis port
TV_MCP_REDIS_PASSWORD
(none)
Redis password, if required
TV_MCP_REDIS_DB
0
Redis database index
TV_MCP_REDIS_KEY_PREFIX
tradingview-mcp:
Key prefix for cached entries
TV_MCP_REDIS_TTL_QUOTE
5
Quote cache TTL in seconds
TV_MCP_REDIS_TTL_STATE
5
Chart state cache TTL in seconds
TV_MCP_REDIS_TTL_OHLCV
60
OHLCV cache TTL in seconds
Development
npm install
npm run build # tsc to dist/
npm run dev # tsc --watch
npm test # vitest run
npm run test:coverage # with v8 coverage report
npm run typecheck # tsc --noEmit
Create a new file under src/tools/ (or extend an existing one).
Export <name>Input and <name>Output Zod schemas plus the handler function.
Add the entry to TOOLS in src/tools/index.ts.
Add a test under tests/.
That's it — auto-registered, auto-validated, auto-introspectable.
Version compatibility
TradingView Desktop
tradingview-mcp
Status
2026.x.x
0.1.x
Tested
If TradingView updates and tools start failing, check connection/tradingview.ts first — that's the single file that knows about TradingView's internal API.
Disclaimer
This software is provided "as is" without warranty of any kind. By running it, you acknowledge:
You are using your own paid TradingView Desktop instance, against your own data.
You enabled the Chrome DevTools debug port yourself.
TradingView's internal API is undocumented and may break.
Nothing in this software guarantees correctness of trading decisions made by an AI agent on top of it. Use it on a paper account before letting it touch real capital.
This is a fresh implementation — built from scratch with the goal of being small, well-typed, and easy to read. If you've worked on similar tools in this space, thanks for paving the way.
T
Tradingview
pueschel88·134 स्टार·
Tradingview MCP server for controlling Tradingview Desktop from Claude Code via Chrome DevTools Protocol
अभी टूल सूची नहीं है। रिमोट सर्वर को पहले हेल्थ चेक के बाद सूची मिलती है।
FAQ
सवाल
Tradingview कैसे इंस्टॉल करें?
इस पेज पर Cursor, Claude Desktop, Claude Code या VS Code के लिए stdio कॉन्फ़िग कॉपी करें। यह पब्लिशर का इंस्टॉल इस्तेमाल करता है, PlugMCP प्रॉक्सी नहीं।
क्या Tradingview के लिए API key चाहिए?
इस रिकॉर्ड में कोई ज़रूरी एनवायरनमेंट वेरिएबल दर्ज नहीं है।
Tradingview कौन सा ट्रांसपोर्ट इस्तेमाल करता है?
Tradingview stdio पर लोकल चलता है।
Tradingview की पिछली जाँच कब हुई थी?
पिछली जाँच 2026-10-28 को हुई। Tradingview MCP server for controlling Tradingview Desktop from Claude Code via Chrome DevTools Protocol