quantower-mcp
Related Servers
Alternatives to quantower-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to read and control TradingView Desktop charts in real time, supporting chart analysis, Pine Script development, alerts, replay practice, and multi-pane automation.45 npmMIT
- FlicenseBqualityBmaintenanceEnables AI-assisted chart analysis, Pine Script development, and live order execution on TradingView Desktop via Chrome DevTools Protocol, supporting connected brokers for trading workflows.9745 npm-
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to control and read data from TradingView Desktop, including morning briefs, chart analysis, Pine Script development, and replay mode.45 npm-
- FlicenseNot gradedqualityBmaintenanceEnables AI assistants to interact with local TradingView Desktop charts via Chrome DevTools Protocol for chart analysis, Pine Script development, and workflow automation. All data stays local, requiring a valid TradingView subscription.45 npm-
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants and CLI tools to read and control a locally running TradingView Desktop app via Chrome DevTools Protocol, including morning briefs, chart navigation, indicator analysis, Pine Script development, alerts, replay practice, and multi-pane layouts.45 npm1-
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with TradingView Desktop via Chrome DevTools Protocol for chart analysis, Pine Script development, and workflow automation, all locally without external data transmission.45 npm1-
TDQS
Scored across 11 tools
Each tool targets a distinct resource or action: status/diagnostics, connections, accounts, symbol search, quote, history, DOM, positions, orders, order history, and trades. The potentially overlapping get_orders vs get_orders_history vs get_trades are explicitly differentiated (working orders vs terminated orders vs executions).
A consistent quantower_ prefix plus verb_noun pattern (list_*, get_*, search_*) is used across almost all tools. quantower_status breaks the verb_noun pattern but is a minor, understandable deviation for a health-check tool.
11 tools is well-scoped for a trading-platform bridge, covering diagnostics, discovery, market data, and account/order state. Each tool earns its place with no obviously redundant entries.
The surface is read-only (status, list, get, search), yet the server advertises a 'trading' mode; there are no place_order, cancel_order, or modify_order tools. Core read workflows are covered, but the trading side of the stated domain is a notable gap.