TradingView Unified MCP
Related Servers
Alternatives to TradingView Unified MCP
No user-submitted related servers found.
Related Servers
- 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 gradedqualityBmaintenanceBridges MCP-capable AI assistants to a locally running TradingView Desktop app via Chrome DevTools Protocol, enabling chart analysis, Pine Script development, drawing tools, alerts, and workflow automation through natural language.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.-
- FlicenseNot gradedqualityBmaintenanceEnables reading charts, running morning briefs, developing Pine Scripts, and automating workflows on TradingView Desktop via Chrome DevTools Protocol.51 npm1-
- FlicenseNot gradedqualityDmaintenanceMCP server that connects AI assistants to TradingView Desktop via Chrome DevTools Protocol, enabling chart analysis, Pine Script development, and workflow automation through natural language.51 npm-
- AlicenseAqualityCmaintenanceA type-safe MCP server that enables AI agents to control TradingView Desktop via Chrome DevTools Protocol, allowing chart state reading, symbol/timeframe changes, and OHLCV data fetching.1151 npm1MIT
TDQS
Scored across 180 tools
The tool surface is organized into clear domains, and many descriptions explicitly distinguish similar operations. However, with 180 tools there are several clusters where boundaries blur, such as alert_prepare/create/validate/verify/reconcile, strategy_scan/sweep/capture/wait, batch_execute/job_submit/workflow tools, and chart_get_state/health/wait_ready. An agent can usually disambiguate by reading descriptions, but misselection risk is significant.
Almost all tools use snake_case with a domain prefix plus an action, such as chart_set_symbol, alert_create, layout_save, and watchlist_add. Minor deviations exist in generic names like batch_execute, job_submit, stream_start, and quote_get, but the overall convention remains predictable and readable.
The server exposes 180 tools, far beyond the typical well-scoped range of 3-15 and well past any reasonable single-server surface. Even for a unified TradingView automation server, this volume creates severe cognitive load, increases overlap, and makes tool selection unwieldy.
Coverage is very broad: charts, panes, layouts, indicators, alerts, Pine scripts, strategies, drawings, watchlists, study templates, paper trading, quotes, screeners, jobs, streams, and research utilities all have lifecycle operations. Some gaps are intentional, such as no real broker order submission or webhook delivery testing, but overall the surface is highly complete for the stated domain.