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 installUse 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:e2eThose commands delegate to versions/v1.
For direct version-line work:
cd versions/v1
npm test
npm run test:remotenpm run test:e2e requires TradingView Desktop running with Chrome DevTools Protocol enabled on port 9222.
- Active branch:
v1. - Default GitHub branch:
v1. mainis not used in this fork.- Historical or upstream references should be tags or external remotes only when intentionally needed; they should not appear as active product branches.
See docs/BRANCHES.md.
Source-available proprietary software. See LICENSE.