TradingView MCP システム ・ フェロックス ラボ

取引チャートから望むAIを売りましょう。 画面で確認します。

TVControl は、TradeView デスクトップを話せるものに変えます。 5mと15mのSPY、QQ、IWMを横断する文章(「このチャートを想定する」、「最後の3月バーを通り抜けてブレイクアウトを呼び出す」)とAIが読み、クリック、タイプ、コンパイル、スクリーンショットを機械の実際の取引ビューアプリ内で読み込みます。 コピーペーストなし、TVControl 操作クラウド バックエンドなし。 TradingView デスクトップと明示的に選択したパブリック API ヘルパーは、ドキュメントとして TradingView と通信します。

すべてのChromiumアプリ、TradeView Desktopが含まれているため、組み込みのデバッグインターフェイス(同じ1つのChromeはそれ自体をデバッグするために使用します)で出荷されます。 TVControlは、モデルコンテキストプロトコルを話す任意のエージェントに**113のチャートコントロールと診断ツールを提示し、あなたの代わりにインターフェイスを話すことを話します。 クライアント・ニュートラル: stdio ワークで MCP サーバを起動できるもの、また、複数の場所で日常的に利用できます。 パインスクリプトのペアプログラム。 パラメータグリッドを最適化します。 グラフのセットアップ全体をスナップショットして復元します.

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.