tradingview-mcp

A Model Context Protocol (MCP) server that lets AI assistants interact with TradingView — real-time quotes, historical OHLCV data, screener, alerts, watchlists, news, chart layouts, Pine scripts, and more. Connect it to Claude Desktop, Cursor, or any MCP-compatible client and interact with TradingView using natural language.

Disclaimer: This project uses TradingView's internal, undocumented web API. It is not affiliated with or endorsed by TradingView. API endpoints may change without notice. Use in accordance with TradingView's Terms of Service.

How It Works

TradingView's web app communicates with its backend over a private REST API and a proprietary WebSocket protocol. This server:

1. Authenticates using a headless Chromium browser (via Playwright) to replicate the normal login flow and obtain valid session cookies.

2. Persists those cookies to disk so re-authentication only happens when the session expires (~25 days).

3. Exposes MCP tools that make authenticated HTTP requests to TradingView's internal endpoints, plus a WebSocket connection for historical OHLCV data.

MCP Client (Claude, Cursor…)
        │  MCP protocol (stdio)
        ▼
  tradingview-mcp
        │  HTTPS + session cookies        WebSocket (OHLCV)
        ▼                                        ▼
  tradingview.com REST API       prodata.tradingview.com

Related MCP server: tradingview-mcp

Features

• Market Data — real-time quotes and detailed symbol info (P/E, EPS, beta, sector, 52-week range, etc.)

• Historical Data — OHLCV candles via TradingView's WebSocket protocol

• Screener — filter stocks, crypto, and forex by price, fundamentals, and technicals

• Alerts — list and inspect price alerts

• Watchlists — list, create, rename, add/remove symbols, and delete watchlists

• News & Ideas — latest headlines per symbol, community ideas search, trending ideas

• Chart Layouts — list and inspect saved chart layouts

• Pine Scripts — list and retrieve source code for saved indicators and strategies

• Account — account details

• Session persistence — logs in once via headless browser, reuses cookies for subsequent runs

Installation

Option A — Docker (recommended)

No Node.js required. Uses the published multi-platform image (linux/amd64 + linux/arm64).

1. Authenticate once

docker run --rm \
  -v tradingview-mcp-session:/data \
  -e TV_USERNAME=your@email.com \
  -e TV_PASSWORD=yourpassword \
  -e TV_SESSION_FILE=/data/.tv_session.json \
  mikeh1975/tradingview-mcp:login

This runs a headless Chromium browser, logs into TradingView, and saves the session cookies to a named Docker volume. You only need to redo this when the session expires (~25 days).

2. Configure Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "tradingview": {
      "command": "docker",
      "args": [
        "run", "--rm", "-i",
        "-v", "tradingview-mcp-session:/data",
        "-e", "TV_SESSION_FILE=/data/.tv_session.json",
        "mikeh1975/tradingview-mcp:latest"
      ]
    }
  }
}

Restart Claude Desktop. You should see "tradingview" in the MCP tools list.

Option B — Local (Node.js)

Requirements: Node.js 18+, a TradingView account.

git clone https://github.com/mikeh-22/tradingview-mcp.git
cd tradingview-mcp
npm install
npx playwright install chromium
npm run build

Configure Claude Desktop:

{
  "mcpServers": {
    "tradingview": {
      "command": "node",
      "args": ["/absolute/path/to/tradingview-mcp/dist/index.js"],
      "env": {
        "TV_USERNAME": "your_username_or_email",
        "TV_PASSWORD": "your_password"
      }
    }
  }
}

On the first run, a headless Chromium browser opens and logs in using your credentials. Session cookies are saved to .tv_session.json. All subsequent runs skip the browser entirely.

To force a fresh login, delete .tv_session.json or call the reset_session tool.

Available Tools

Market Data

get_quote

Returns real-time price data for one or more symbols.

get_symbol_info

Returns detailed fundamental and technical data for a single symbol (P/E, EPS, 52-week high/low, beta, sector, dividends, etc.).

get_ohlcv

Returns historical OHLCV candlestick data via TradingView's WebSocket protocol.

Screener

screen_stocks

Screens US equities using price, volume, fundamental, and technical filters.

screen_crypto

Screens crypto assets. Same parameters as screen_stocks.

screen_forex

Screens forex pairs. Same parameters as screen_stocks.

get_screener_fields

Returns a reference list of all available screener field names, grouped by category (price, volume, fundamentals, technicals, volatility, metadata).

(no parameters)

Filter object format:

{ "left": "market_cap_basic", "operation": "greater", "right": 1000000000 }

Supported operations: greater, less, greater_or_equal, less_or_equal, equal, not_equal, in_range, not_in_range, in, not_in, crosses_up, crosses_down

For in_range, right should be [min, max]. Example — RSI between 30 and 50:

{ "left": "RSI", "operation": "in_range", "right": [30, 50] }

Alerts

list_alerts

Returns all alerts on your account.

(no parameters)

get_alert

Returns full details for a single alert.

Watchlists

list_watchlists

Returns all watchlists with their symbols.

(no parameters)

get_watchlist

Returns a single watchlist and its full symbol list.

create_watchlist

Creates a new watchlist, optionally pre-populated with symbols.

rename_watchlist

Renames an existing watchlist.

add_symbols

Adds one or more symbols to a watchlist.

remove_symbols

Removes one or more symbols from a watchlist.

delete_watchlist

Permanently deletes a watchlist.

News & Ideas

get_news

Returns the latest news headlines for a symbol.

search_ideas

Searches published TradingView chart ideas.

get_trending_ideas

Returns trending TradingView chart ideas.

Chart Layouts

list_layouts

Returns all saved chart layouts.

(no parameters)

get_layout

Returns details of a saved layout including its name, symbol, and resolution.

Pine Scripts

list_scripts

Returns Pine Script indicators and strategies.

get_script

Returns the Pine Script source code for a script by ID.

Account

get_account

Returns your TradingView account details.

(no parameters)

Session

reset_session

Clears the saved session. The next tool call will trigger a fresh Playwright login.

(no parameters)

Symbol Format

TradingView uses an EXCHANGE:TICKER format for all symbols:

Project Structure

src/
├── index.ts       # MCP server entrypoint — tool definitions and request handlers
├── auth.ts        # Playwright login flow — opens headless browser, extracts cookies
├── client.ts      # HTTP client — fetch wrapper with cookie jar, CSRF, and subdomain support
├── types.ts       # Shared TypeScript interfaces
├── alerts.ts      # Alert read operations
├── watchlists.ts  # Watchlist CRUD
├── market.ts      # Quotes and symbol info
├── ohlcv.ts       # Historical OHLCV via TradingView WebSocket protocol
├── screener.ts    # Stock/crypto/forex screener
├── news.ts        # News headlines and community ideas
├── layouts.ts     # Chart layout read operations
├── scripts.ts     # Pine Script source retrieval
└── account.ts     # Account info

Troubleshooting

Login fails / Playwright times out

TradingView's login page may show a CAPTCHA or 2FA prompt. Try setting headless: false in src/auth.ts to watch the browser and identify what's blocking the flow.

API requests return 403 or 401

Your session has likely expired. Delete .tv_session.json (or call reset_session) to trigger a fresh login. With Docker, re-run the login container.

API requests return 404 or unexpected shapes

TradingView's internal API is undocumented and may change without notice. Open your browser's DevTools → Network tab, perform the action manually on tradingview.com, and compare the request URL and payload against the relevant file in src/.

get_ohlcv times out

The WebSocket connection to prodata.tradingview.com may be blocked by a firewall, or the symbol format may be incorrect. The timeout is 30 seconds.

TV_USERNAME / TV_PASSWORD not found

When running via Claude Desktop, set credentials in the env block of your MCP config rather than relying on a .env file — the server process won't automatically source it.

CI/CD

Images published to Docker Hub:

• mikeh1975/tradingview-mcp:latest — MCP server (runtime image, no browser)

• mikeh1975/tradingview-mcp:login — Login helper (includes Playwright + Chromium)

License

MIT