TradingView MCP
Related Servers
Alternatives to TradingView MCP
No user-submitted related servers found.
Related Servers
- AlicenseCqualityCmaintenanceEnables an MCP client to drive a local Chrome, Chromium, or Edge browser session to read and modify TradingView charts — saved layouts, alerts, Pine scripts, Strategy Tester reports, OHLCV and quote data, watchlists, drawings, replay, plus local research and paper-trading simulation — through 185 tools with a read-only mode and configurable mutation controls. Changes are gated on exact browser targets and layout IDs, and the server runs as a dependency-free local stdio or authenticated loopback HTTP process.180MIT
- FlicenseNot gradedqualityBmaintenanceEnables remote MCP clients to automate a headless TradingView chart via HTTP/SSE, exposing 84 tools for chart navigation, market data and indicators, Pine Script, drawings, screenshots, alerts, watchlists, replay, and batch operations.51 npm-
- FlicenseNot gradedqualityCmaintenanceProvides unified TradingView capabilities through one MCP server, including market data, screening, technical analysis, backtesting, sentiment, chart control via browser automation, Pine script transpilation and compilation, and alert webhooks.-
- AlicenseAqualityCmaintenanceEnables MCP clients to retrieve TradingView market data, including historical OHLCV candles, quotes, technical indicators, and screener results over stdio or SSE.4MIT
- AlicenseNot gradedqualityAmaintenanceA local MCP server that connects TradingView Desktop to AI assistants via Chrome DevTools Protocol, enabling Pine Script development, multi-timeframe analysis, and Wyckoff scanning with a rules engine.44 npm1MIT
- AlicenseNot gradedqualityCmaintenanceA local-first MCP server that bridges AI coding agents with MetaTrader 5 for inspection, market data, MQL5 development, compiling, Strategy Tester review, workspace sync, logs, audit trails, demo trading, and carefully gated live trading.MIT
TDQS
Scored across 38 tools
The tool set is grouped by clear prefixes (market_, chart_, tradingview_), and most tools target distinct resources, but there is notable overlap between market_get_ta and chart_analyze, and between individual chart_add_* tools and chart_apply_overlays. Agents may struggle to choose between quote, price, and snapshot variants or between one-call convenience workflows and the underlying primitive tools.
Most tools follow a consistent verb_noun pattern within each prefix group, such as market_get_price, chart_add_indicator, and tradingview_get_history. A few deviations like market_search, market_screen, chart_open, and tradingview_close are minor and do not undermine the overall readability.
At 38 tools, the surface is too large for an agent to navigate efficiently, even though the set is organized into three coherent subdomains. Several tools could be consolidated—for example, the many individual chart_add_/remove_ tools alongside chart_apply_overlays and chart_clear_overlays, and the multiple market quote/snapshot variants.
The set covers market data retrieval, local chart manipulation, technical analysis, and the official TradingView browser workflow well, including import/export, snapshots, and lifecycle management. Minor gaps exist, such as no explicit removal of an indicator in the official TradingView browser and no obvious bulk snapshot workflow, but these can be worked around.