Setup Guide¶
Prerequisites¶
- Node.js 18+
- Google Chrome (for CDP)
- TradingView account (Pro+ recommended for multiple indicators)
- Claude Code CLI
Step 1: Launch Chrome with CDP¶
Close ALL Chrome instances first, then:
"C:\Program Files\Google\Chrome\Application\chrome.exe" --remote-debugging-port=9222 --user-data-dir="%USERPROFILE%\ChromeCDP" https://www.tradingview.com/chart
Or use the batch script:
tradingview-mcp/scripts/launch_chrome_cdp.bat
Important:
- --user-data-dir must point to a NON-default Chrome profile
- First launch: log into TradingView in the new profile
- Load your indicators once they are built and ready
Step 2: Install MCP Server¶
cd tradingview-mcp
npm install
Step 3: Configure Claude Code¶
Add to ~/.claude/.mcp.json:
{
"mcpServers": {
"tradingview": {
"command": "node",
"args": ["C:/Users/User/Desktop/TradingDesk/tradingview-mcp/src/server.js"]
}
}
}
Step 4: Verify Connection¶
In Claude Code:
Use tv_health_check to verify the connection
Expected: Connected, chart state with symbol and timeframe.
Step 5: Start Dashboard (Optional)¶
cd fatbot
node dashboard/server.js
# Open http://localhost:8000
Troubleshooting¶
| Problem | Solution |
|---|---|
| CDP won't connect | Ensure all Chrome instances closed before launching with CDP flag |
| "No chart found" | Navigate to a chart page in Chrome (tradingview.com/chart) |
| Indicator data empty | Ensure indicators are loaded and visible on chart |
| Tools return errors | Run tv_discover to check which API paths are alive |
| TradingView Desktop won't work | MSIX v3.0.0 needs COM API launcher — run scripts\launch_tv_debug.bat (see chrome-cdp.md) |