TradingView Chrome MCP
Related Servers
Alternatives to TradingView Chrome MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to drive a live TradingView chart in Chrome, turning natural-language trading ideas into compiled Pine Script indicators, adding them to charts, and reading back results. It also supports chart navigation, indicator management, screenshots, and strategy tester backtest results.69-
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to read, control, and draw on locally running TradingView Desktop charts via Chrome DevTools Protocol for chart analysis, Pine Script development, and workflow automation.111 npm-
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to control a logged-in TradingView chart in Chrome, including writing and compiling Pine Script indicators, adding them to charts, changing symbols and timeframes, capturing screenshots, and retrieving strategy tester results.-
- FlicenseNot gradedqualityBmaintenanceEnables AI assistants to connect to a locally running TradingView Desktop app via Chrome DevTools Protocol for chart analysis, Pine Script development, drawing, alert management, replay, and chart navigation through natural language.111 npm-
- FlicenseNot gradedqualityCmaintenanceConnects AI assistants to TradingView Desktop via Chrome DevTools Protocol for AI-assisted chart analysis, Pine Script development, and workflow automation.111 npm3-
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to interact with TradingView Desktop charts via Chrome DevTools Protocol for chart analysis, Pine Script development, and workflow automation.111 npm-
TDQS
Scored across 60 tools
Several tools are exact or near duplicates: tv_status/tv_read_chart, tv_pine_create/tv_pine_patch, and tv_watchlist_sync heavily overlaps tv_watchlist_read and tv_watchlist_add_symbol. With 60 tools, agents are likely to misselect between these ambiguous pairs despite mostly distinct domains.
The tv_* tools follow a consistent verb_noun pattern such as tv_change_symbol, tv_layout_save, and tv_indicator_add. The main deviations are the non-tv system/utility tools like ping, emergency_stop, browser_status, and sync_status, plus the British spelling of licence_status/activate_licence.
60 tools is too many for a well-scoped MCP surface, even though TradingView automation is a broad domain. The set includes redundant aliases and admin utilities that could be consolidated, making the tool count feel padded rather than purposeful.
Core workflows are well covered: chart state, OHLCV data, Pine editor lifecycle, alerts, layouts, indicators, watchlist, and strategy testing all have supporting tools. However, there are notable dead ends: drawings can only be added with no listing/removal, watchlist has no remove operation, alerts lack update, and layouts have no delete.