trading-crew-mcp
Related Servers
Alternatives to trading-crew-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables Claude to control and read from the TradingView Desktop app, providing automated morning briefs, chart analysis, Pine Script development, and replay mode.-
- FlicenseNot gradedqualityCmaintenanceConnects Claude Code to a locally running TradingView Desktop app via Chrome DevTools Protocol, enabling AI-assisted chart navigation, Pine Script development, drawing, alerts, replay, and screenshots through natural language.88 npm-
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to connect to a locally running TradingView Desktop app to analyze charts, develop Pine Scripts, navigate symbols and timeframes, draw annotations, manage alerts, and automate chart workflows.88 npm-
- FlicenseNot gradedqualityDmaintenanceEnables Claude to control TradingView Desktop for automated morning briefs, chart analysis, Pine Script development, and session management via MCP tools.88 npm-
- FlicenseNot gradedqualityDmaintenanceConnects Claude Code to your local TradingView Desktop app via Chrome DevTools Protocol, enabling AI-assisted chart analysis, Pine Script development, and workflow automation.88 npm-
- FlicenseNot gradedqualityDmaintenanceEnables an AI assistant to interact with a locally running TradingView Desktop app for chart navigation, indicator and price analysis, Pine Script development, drawing, alerts, replay practice, screenshots, and workflow automation via Chrome DevTools Protocol.88 npm-
TDQS
Scored across 21 tools
Most tools target a distinct resource+action (draw_* vs list/get/remove/clear_drawings, alerts CRUD, chart control, data reads). A few pairs are close: draw_trend_line vs draw_chain (single line vs connected pivot chain), and find_pivots vs suggest_chain (raw swings vs a validated chain), but the descriptions clearly separate these by input/output and purpose (suggest_chain explicitly hands off points to draw_chain). get_candles vs save_candles is well delineated by the 500-candle cap and file-export intent.
Almost all names follow a verb_noun or verb_noun_noun pattern (draw_trend_line, set_timeframe, list_alerts, create_alert, delete_alert, save_candles). The only deviations are the noun-style chart_health and screenshot, which break the verb-first convention but remain unambiguous. Minor deviation overall, not confusing.
At 21 tools the surface is at the upper end of what an agent can hold comfortably; the rubric's 16-25 band is borderline heavy. Each tool does earn a place (7 drawing, 5 data, 5 alerts, 4 chart/screenshot), so it is justified by breadth of functionality rather than padding. Still, some consolidation (e.g. a single draw tool with a type parameter, or merging get_drawing into list_drawings) could trim the set.
Drawings have full lifecycle (multiple create types, list, get, remove, clear) and alerts have near-complete CRUD plus fired-history, with data reads, pivots, screenshots, and chart state all covered. Notable gaps: no way to edit/move an existing drawing (only delete and redraw), no alert enable/disable toggle despite 'active' being listed, and no tool to change the chart symbol (only timeframe), which agents might expect on a trading server. These are workable around but real.