tradingview-mcp — What is it?

The tradesdontlie/tradingview-mcp project provides an AI-assisted bridge between TradingView Desktop and Claude Code, enabling personal workflow automation and Pine Script development with AI assistance.

⭐ 266 Stars 🍴 67 Forks JavaScript Author: tradesdontlie
Source: README View on GitHub →

Why it matters

This project is gaining attention due to its innovative approach to integrating AI with trading platforms, addressing the need for automated analysis and development in financial markets. It fills a gap by providing a tool that allows for AI-assisted Pine Script development and chart analysis, which is unique in its use of the Chrome DevTools Protocol for local communication.

Source: Synthesis of README and project traits

Core Features

AI-assisted Pine Script development

Facilitates writing, injecting, compiling, debugging, and iterating on scripts with AI assistance, enhancing the efficiency of script development.

Source: README
Chart navigation and analysis

Enables users to change symbols, timeframes, zoom, add/remove indicators, and perform visual analysis, with the ability to read indicator values and annotations.

Source: README
Drawing and alert management

Supports drawing on charts, managing alerts, and replaying historical data for practice, enhancing the user's ability to interact with the chart interface.

Source: README
Multi-pane layouts and monitoring

Allows users to set up multi-pane layouts and monitor their charts through streaming JSONL data, providing a comprehensive view of the trading environment.

Source: README

Architecture

The architecture is inferred to be modular, with a clear separation of concerns. It likely employs design patterns such as the Model-View-Controller (MVC) for managing interactions between the AI, the TradingView Desktop app, and the user interface. The code tree indicates a structured module decomposition, with distinct directories for CLI commands, chart analysis, and Pine Script development. Data flow is managed through the Chrome DevTools Protocol, and key technical decisions include the use of Electron for the TradingView Desktop integration and the @modelcontextprotocol/sdk for communication.

Source: Code tree + dependency files

Tech Stack

infra: Local machine with TradingView Desktop and Node.js environment  |  key_deps: @modelcontextprotocol/sdk, chrome-remote-interface  |  language: JavaScript  |  framework: Electron, Chrome DevTools Protocol

Source: Dependency files + code tree

Quick Start

git clone https://github.com/tradesdontlie/tradingview-mcp.git cd tradingview-mcp npm install ./scripts/launch_tv_debug_mac.sh Add to Claude Code MCP config: { "mcpServers": { "tradingview": { "command": "node", "args": "/path/to/tradingview-mcp/src/server.js" } } } Verify connection with tv_health_check.
Source: README Installation/Quick Start

Use Cases

This project is for developers and researchers interested in AI-assisted financial analysis and Pine Script development. It is useful in scenarios where automated analysis and script development are required, such as in financial market research, algorithmic trading, and educational purposes.

Source: README

Strengths & Limitations

Strengths

  • Strength 1: Innovative integration of AI with trading platforms
  • Strength 2: Enables automated analysis and script development
  • Strength 3: Local data processing for enhanced security

Limitations

  • Limitation 1: Requires a valid TradingView subscription
  • Limitation 2: May be affected by changes in TradingView's internal structure
  • Limitation 3: Limited to local machine usage
Source: Synthesis of README, code structure and dependencies

Latest Release

Not enough information.

Source: GitHub Releases

Verdict

The tradesdontlie/tradingview-mcp project is worth watching for its innovative approach to integrating AI with trading platforms. It is particularly suitable for developers and researchers interested in exploring the intersection of AI and financial markets, offering a unique tool for automated analysis and script development.

Transparency Notice
This page is auto-generated by AI (a large language model) from the following public materials: GitHub README, code tree, dependency files and release notes. Analyzed at: 2026-04-19 10:42. Quality score: 85/100.

Data sources: README, GitHub API, dependency files