TradingView MCP 시스템 · Ferrox Labs

** TradingView 차트에서 원하는 AI를 선택하십시오. 화면에서 발생합니다.**

TVControl는 당신이 말할 수있는 무언가로 TradingView 데스크탑을 전환합니다. 당신은 문장을 입력 (* “이 차트를 요약”*, “SPY, QQ 및 IWM 5m 및 15m에 걸쳐이 전략을 요약”, “바로 마지막 3 월 바를 통해 단계 및 브레이크 아웃을 호출”) 및 AI 읽기, 클릭, 유형, 컴파일 및 스크린 샷 내부 실제 TradingView 응용 프로그램에. TVControl-operated 클라우드 백업 없음. TradingView Desktop 및 명시적으로 선택한 public-API 헬퍼는 여전히 TradingView와 문서로 통신합니다.

그것은 모든 크롬 응용 프로그램, TradingView 데스크톱 포함, 내장 디버깅 인터페이스와 선박 (다른 크롬은 직접 디버깅에 사용). TVControl은 대신 인터페이스를 말한다, exposing **113 차트 제어 및 진단 도구 ** 모델 Context 프로토콜을 말하는 모든 에이전트에. 그것은 클라이언트 중립: stdio 일에 MCP 서버를 발사할 수 있는 무엇이든, 그리고 그것은 몇몇의 맞은편에 매일 사용에서 입니다. Pine Script의 페어 프로그램. 모수 격자를 낙관하십시오. Snapshot 및 전체 차트 설정 복원.

TVControl

TradingView MCP System · by Ferrox Labs

Tell your AI what you want from your TradingView chart. Watch it happen on screen.

TVControl turns your TradingView Desktop into something you can talk to. You type a sentence (“summarise this chart”, “sweep this strategy across SPY, QQQ and IWM on 5m and 15m”, “step through last March bar by bar and call out the breakout”) and the AI reads, clicks, types, compiles and screenshots inside the actual TradingView app on your machine. No copy-paste and no TVControl-operated cloud backend. TradingView Desktop and explicitly selected public-API helpers still communicate with TradingView as documented.

It works because every Chromium app, TradingView Desktop included, ships with a built-in debugging interface (the same one Chrome uses to debug itself). TVControl speaks that interface on your behalf, exposing 113 chart-control and diagnostic tools to any agent that speaks the Model Context Protocol. It is client-neutral: anything that can launch an MCP server over stdio works, and it is in daily use across several. Pair-program in Pine Script. Optimize parameter grids. Snapshot and restore whole chart setups. Drive 4-pane layouts. Step through replay. Scan a watchlist. All by speech-to-action.

113 MCP tools · 938 deterministic offline tests · 10 verify scripts · 9 prompt-library workflows · no TVControl cloud backend. Everything in this repo is real, tested, and used daily.

What is new in 2.5

The 2.5 line is about one thing: a tool must build its answer from an independent read, never from the request or from the response of the thing it just did. Every fix below is a place where that was not true.

• A result you can act on when a call times out. chart_set_symbol and chart_set_timeframe had already applied the change by the time their readiness wait expired, then threw as though nothing had happened, so a caller that retried applied it twice. They now return chart_ready: false and say not to retry. indicator_add_from_search polls for the study instead of sleeping 1500ms and guessing. The contract is now stated in the tool descriptions: a thrown error means nothing changed.
• pine_open no longer risks the wrong script. It fetched a script’s source and pasted it into whatever buffer was open, leaving the editor bound to the previous script while reporting success. A following save wrote over the wrong file. It now reads the editor’s own title back and refuses on a mismatch. New in this release: pine_get_script_source reads a saved script over the REST API without touching the editor at all, which is what you want for comparing a saved script against a local file.