Skip to main content
Glama
GlynnCarson

tradingview-mcp

by GlynnCarson

Related Servers

Alternatives to tradingview-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that lets AI assistants interact with TradingView for real-time quotes, historical OHLCV data, screener, alerts, watchlists, news, chart layouts, Pine scripts, and more. Connect it to Claude Desktop, Cursor, or any MCP-compatible client to control TradingView via natural language.
      115 npm
      5
      -
    • A
      license
      A
      quality
      B
      maintenance
      MCP server for TradingView's market screener API, enabling stock, forex, crypto, and ETF screening, technical analysis, and investor workflows via Claude or CLI.
      12
      297 npm
      53
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Provides 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.
      -
    • F
      license
      Not graded
      quality
      B
      maintenance
      A comprehensive MCP server that integrates TradingView Desktop automation, screener API, Yahoo Finance, IDX/BEI tools, backtesting, news sentiment, trade math, and market sessions. It enables traders to perform technical analysis, backtest strategies, manage positions, and automate TradingView tasks through natural language.
      -

    TDQS

    B3.4/5.0

    Scored across 44 tools

    Disambiguation2/5

    Several tools have overlapping purposes, such as the volume scanners (volume_breakout_scanner, volume_confirmation_analysis, smart_volume_scanner), the EGX sector tools (egx_sector_scan, egx_sector_scanner), and the multiple backtesting tools. While descriptions attempt to differentiate, an agent could easily miscategorize or select the wrong tool.

    Naming Consistency4/5

    The naming convention is predominantly snake_case, which is consistent. However, minor inconsistencies exist, such as 'egx_sector_scan' vs 'egx_sector_scanner' and varying suffixes like 'analysis', 'scanner', 'scan', which slightly reduces clarity.

    Tool Count2/5

    With 44 tools, the server is overpopulated. Many tools could be consolidated (e.g., volume scanners into one parameterized tool, backtests into a unified interface). The high count suggests a lack of modularization, making the surface area difficult to navigate.

    Completeness4/5

    The server covers a broad spectrum: EGX-specific tools, general scanners, individual analysis, multi-timeframe, sentiment, news, combined analysis, backtesting, paper trading, market regime, crypto, stocks, futures, and options. Minor gaps (e.g., fundamental data, advanced order types) exist, but overall the domain is well-covered.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive