loading…
Search for a command to run...
loading…
Enables automated control of TradingView Desktop via Chrome DevTools Protocol with 78+ tools for chart manipulation, Pine Script development, and indicator anal
Enables automated control of TradingView Desktop via Chrome DevTools Protocol with 78+ tools for chart manipulation, Pine Script development, and indicator analysis. Supports automated morning briefs for session bias generation, replay trading practice, and multi-pane layouts with secure local-only data processing.
Español · Release v1.0.2 · Repository history
Local TradingView Desktop MCP bridge for chart automation, Pine workflows, Codex support, and consent-gated trading actions.
This repository follows the same product-line layout used by Kerebrom: stable implementation lines live under versions/vN/, while the repository root stays as the product landing page and operational guide.
| Line | Status | Product root | Purpose |
|---|---|---|---|
v1 |
current | versions/v1/ |
TradingView Desktop MCP bridge, 100+ tools, offline/remote/live test split, hardened launcher. |
git clone https://github.com/ulianbass/tradingview-mcp.git
cd tradingview-mcp/versions/v1
npm install
Use this MCP server path in AI clients:
/absolute/path/to/tradingview-mcp/versions/v1/src/server.js
For this machine, the current path is:
/Users/ulianbass/Documents/TradingView MCP/versions/v1/src/server.js
From the repository root:
npm test
npm run test:remote
npm run test:e2e
Those commands delegate to versions/v1.
For direct version-line work:
cd versions/v1
npm test
npm run test:remote
npm run test:e2e requires TradingView Desktop running with Chrome DevTools Protocol enabled on port 9222.
v1.v1.main is not used in this fork.See docs/BRANCHES.md.
Source-available proprietary software. See LICENSE.
Run in your terminal:
claude mcp add tradingview-mcp -- npx CSA PROJECT - FZCO © 2026 IFZA Business Park, DDP, Premises Number 31174 - 001
Security
Low riskAutomated heuristic from public metadata — not a security guarantee.