TradingView MCP is a Model Context Protocol server that exposes TradingView market data, multi-exchange screeners, technical analysis, sentiment, news, and a backtesting engine to MCP clients such as Claude Desktop, Cursor, and Copilot. It is an independent project that uses public TradingView scanner and chart endpoints, so no TradingView account or API key is required.
The server is written in TypeScript with a layered design: an MCP router validates inputs and returns JSON, domain services hold the business logic, and a screener provider is an HTTP client with retry, jitter, and throttling. Caching is in-memory by default with an optional Redis backend; if Redis is unreachable at startup the server falls back to in-memory storage automatically. Errors are returned as structured envelopes with stable error codes.
Data sources include the TradingView scanner API for screeners, Yahoo Finance for quotes and OHLCV, the Reddit JSON API for sentiment, and financial RSS feeds for news. A combined-analysis tool fetches technical, sentiment, and news data in parallel and returns a confluence summary for a symbol.
Features
- Multi-exchange screeners: crypto, US equities, EGX, BIST, HKEX, SSE, TWSE, and others via per-exchange symbol lists and the scanner API
- Technical analysis: Bollinger ratings, RSI, multi-timeframe alignment, volume breakouts, and candle patterns
- Backtesting: nine strategies with Sharpe and Calmar metrics and walk-forward overfitting detection using historical Yahoo Finance data
- Market intelligence: Reddit sentiment scores, RSS financial news, and Yahoo Finance quotes
- MCP tools: 36 tools over the stdio transport for MCP-compatible hosts
- Caching: in-memory by default, optional Redis for distributed caching, with configurable fresh and stale TTLs
- Resilience: retry with backoff, request throttling, and structured error envelopes
- Configuration: Zod-validated environment variables for logging, cache TTLs, retry delays, concurrency caps, and an optional rotating proxy
