TradingView Alerts MCP Server
Related Servers
Alternatives to TradingView Alerts MCP Server
No user-submitted related servers found.
Related Servers
- 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 gradedqualityDmaintenanceEnables automated control of TradingView Desktop via MCP, supporting morning briefs, chart analysis, Pine Script development, replay practice, and alert management.120 npm-
- 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.120 npm-
- AlicenseNot gradedqualityDmaintenanceControls the TradingView Desktop app via MCP, allowing AI agents to manage charts, indicators, Pine Script strategies, and optionally mirrors signals to MetaTrader 5 for automated trading.1MIT
- 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.18064MIT
- 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.120 npm-
TDQS
Scored across 9 tools
Each tool targets a distinct action (auth check, list, create, pause, resume, delete, list strategies, list fires, resolve symbol). Overlapping actions like pause/resume/delete are clearly differentiated by their verb and description.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., list_alerts, create_strategy_alert, pause_alerts). Verbs are active and distinct, making the naming predictable.
9 tools is well-scoped for an alerts management server, covering authentication, alert CRUD, strategy discovery, and symbol resolution without unnecessary bloat.
The core alert lifecycle (create, list, pause, resume, delete) is covered, along with supporting tools for strategies and symbol resolution. However, the creation tool is limited to strategy-based alerts, leaving no way to create a simple price alert, which is a minor gap.