TradingView MCP Server

Community

Expose TradingView market data, multi-exchange screeners, and a backtesting engine to AI assistants

How to install ↓ Compare GitHub source repository ↗

Category: Other #57 of 230
Stars: ★ 155 Popular
Transport: stdio (local process)
Runtime: Node.js 18+ · Docker
Credentials: No credential needed
License: MIT
Last commit: 38 days ago

62FMRS · C

A feature-rich independent TradingView MCP server: 36 tools spanning screeners, technical analysis, sentiment, news, and backtesting, built with strict TypeScript, layered architecture, and optional Redis caching, with solid tests and docs; however it is not affiliated with TradingView and backtest results are not financial advice.

Strongest · Documentation 16/20 Weakest · Reliability 8/20

Reliability

8/20

Security and permissions

14/20

Maintenance

11/20

Documentation

16/20

Setup experience

13/20

Why each score

Reliability 8/20: The README claims Vitest unit tests (covering error envelopes, timeframe/exchange validators, cache store behavior) and an `npm run validate` pipeline, plus architecture descriptions of the MCP router, service layer, and a retry/throttle provider, with 36 declared tools. However, no actual source files, CI workflow definitions, or executed test evidence were provided, so it cannot be confirmed that the declared tool list matches real behavior. The README itself states integration tests against live TradingView/Yahoo APIs are intentionally excluded, meaning the key external-dependency paths lack reproducible verification. Per the static-review rule, reliability is capped at 12 without verifiable CI+test evidence; given the incomplete evidence chain, it is scored 8.
Security and permissions 14/20: The server performs mainly read-only market-data retrieval (public TradingView scanner, Yahoo Finance, Reddit JSON, RSS feeds); the FAQ explicitly states no TradingView account or API key is required, and no real secrets or tokens appear in the setup examples. Optional Redis caching and an optional PROXY_ENABLED rotating-proxy feature expand the network surface, but both are off by default and documented, and no irreversible delete/pay/deploy/remote-command defaults are evident, so no red line applies. Since the actual source implementing input handling, SSRF protections, or proxy configuration cannot be inspected, some uncertainty remains, preventing a top score; scored 14.
Maintenance 11/20: The repository carries an MIT license, has 148 stars, only 1 open issue, and is not archived, suggesting some activity, and the README describes a clear contribution workflow (fork, branch, `npm run validate`). However, no release history, changelog, CI badges, dependency-update policy, or dedicated security-response channel are evidenced in the material, so actual commit cadence and issue-response speed cannot be verified — a governance/versioning evidence gap. Scored 11.
Documentation 16/20: The README is comprehensive: table of contents, Mermaid architecture and sequence diagrams, project structure, installation steps, a configuration table with environment-variable defaults, a troubleshooting table, an FAQ, and testing notes — well-layered overall. However, the 36 tools are not individually documented with parameter/schema details (only grouped by category), rate-limit guidance is left to user tuning rather than concrete thresholds, and cost implications are not discussed (though most APIs appear free/public). Deductions are for missing per-tool parameter docs and some limitation disclosures; scored 16.
Setup experience 13/20: Installation steps are clear: Node 18+/npm 9+ requirements, git clone, npm install, npm run build, plus a Claude Desktop JSON config example, Cursor/VS Code guidance, and a Docker Compose option, along with a documented Windows first-launch timeout workaround (pre-building the project). However, per the static-review calibration, setup is capped at 15 absent verifiable CI workflows and committed tests covering key paths; since no such CI configuration could be confirmed in the material, it is scored 13.

Static review · not runListed 2026-09-07

Read the FMRS scoring method →

Fit and risk

What it can accessUses the network

Best for

Traders and quant hobbyists researching market data inside AI assistants
Users of MCP clients such as Claude Desktop and Cursor
Developers who need a cacheable, fault-tolerant market data pipeline

Not for

Users seeking real financial advice or guaranteed returns
Users needing live order execution or brokerage integration
Users expecting an officially certified TradingView server

Required permissions

Access to public scanner.tradingview.com endpoints
Access to Yahoo Finance, Reddit JSON API, and RSS financial feeds
Optional Redis connection (REDIS_URL / host / port)
No TradingView account or API key required

Risks and side effects

Backtests use historical data with simulated costs and do not predict future results
Relies on public endpoints subject to rate limits or upstream failures
Outputs are informational only, not financial advice
Not an official TradingView project

Setup

Before you start

Runtime：Node.js 18+ · Docker

Other optional settings (11)

LOG_LEVEL optional Logging verbosity, default info; see .env.example.

REDIS_ENABLED optional Enable distributed Redis cache, default false.

REDIS_URL optional Full Redis connection URL; falls back to REDIS_HOST/REDIS_PORT when unset.

REDIS_HOST optional Redis host, default 127.0.0.1.

REDIS_PORT optional Redis port, default 6379.

REDIS_KEY_PREFIX optional Cache key namespace prefix, default tradingview-mcp:.

TRADINGVIEW_MCP_CACHE_TTL optional Fresh cache TTL in seconds, default 60.

TRADINGVIEW_MCP_STALE_TTL optional Stale fallback TTL in seconds, default 21600.

TRADINGVIEW_MCP_RETRY_DELAYS optional Retry backoff schedule, default 1.0,4.0.

TRADINGVIEW_MCP_MAX_INFLIGHT optional Cap on concurrent TA requests, default 2.

PROXY_ENABLED optional Enable rotating HTTP proxy, default false.

Requires Node.js 18+, npm 9+, and optionally Redis 6+. Clone the repository, then run npm install and npm run build to produce dist/index.js. In Claude Desktop, set command to node with args pointing at the built binary; in Cursor / VS Code MCP, point the config at the same binary and restart the host. Alternatively use docker compose up -d for a Redis-enabled setup. Configuration is via a .env file (see .env.example) with variables for LOG_LEVEL, REDIS_ENABLED, cache TTLs, retry backoff, concurrency cap, and proxy.

claude_desktop_config.json

{"mcpServers":{"tradingview":{"command":"node","args":["D:/path/to/tradingview-mcp/dist/index.js"]}}}

Shown for Claude Desktop. Other clients may use a different file or key (VS Code uses "servers") — the configurator below converts it.

.vscode/mcp.json

{
  "servers": {
    "tradingview": {
      "command": "node",
      "args": [
        "D:/path/to/tradingview-mcp/dist/index.js"
      ]
    }
  }
}

Goes in your project's .vscode/mcp.json (VS Code uses a "servers" key).

Terminal

claude mcp add tradingview -- node D:/path/to/tradingview-mcp/dist/index.js

Run it in a terminal; replace any <…> placeholders with your own values first.

Generate and validate client config

Check that it works

Run npm install && npm run build, point your MCP client config at dist/index.js and restart the client; the tradingview server's 36 tools (e.g. top_gainers, combined_analysis) should appear in the tool list. Asking for a screener result confirms the connection works.

Troubleshooting

An empty [] result means no symbols matched filters today — adjust filters
ALL_BATCHES_FAILED indicates upstream failure; retry later and check network
On timeouts, reduce batch size and enable caching
Redis outages degrade gracefully to in-memory cache; check REDIS_URL and firewall
Windows first-launch timeout: run npm run build before configuring your MCP host
Requires Node 18+; verify with node --version

Things to try

Once connected, you can ask your AI assistant things like:

List the top crypto gainers on Binance for the current timeframe.
Run a combined analysis on BTC including technical indicators, Reddit sentiment, and the latest financial news.
Backtest AAPL with the momentum strategy and report Sharpe ratio and walk-forward overfitting results.
Scan US equities for volume breakout candidates.

Use cases

Query multi-exchange gainers/losers and screener results via natural language

Run RSI, Bollinger, and multi-timeframe technical analysis

Backtest 9 strategies with Sharpe/Calmar and overfitting detection

Aggregate Reddit sentiment, RSS news, and Yahoo Finance quotes into combined analysis

Supported clients

Claude Desktop

Cursor

Listed from the project's documentation, not tested by this site.

Overview

TradingView MCP Server is a production-oriented open-source Model Context Protocol server exposing 36 tools for TradingView market data, multi-exchange screeners (crypto, US equities, EGX, BIST, HKEX, SSE, TWSE and more), technical analysis (Bollinger ratings, RSI, multi-timeframe alignment, volume breakouts, candle patterns), Reddit sentiment, RSS financial news, Yahoo Finance quotes, and a built-in backtesting engine with 9 strategies including Sharpe, Calmar, and walk-forward overfitting detection. It is an independent open-source project, not affiliated with TradingView Inc.; outputs are for research and education only, not financial advice.

Similar servers

Hevy MCP 77 · B

Manage your Hevy workout data from AI assistants via MCP.

★ 517 · Tools 26 Compare with this →

Firecrawl MCP Server 75 · B

Firecrawl's official MCP server for web search, scraping, and structured extraction for AI agents

★ 7.6k · Tools 11 Compare with this →

BioMCP 75 · B

One binary. One grammar. Evidence from the biomedical sources you already trust.

★ 659 · Tools 11 Compare with this →

Compartment 75 · B

Encrypted, fully offline long-term memory for AI agents

★ 583 · Tools 14 Compare with this →

Compare with other MCP servers

Source revision ea2a80195867 Data synced 2026-10-19 Read the FMRS scoring method