Skip to main content
Glama
Miha21222

tradingview-mcp

by Miha21222
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to tradingview-mcp

No user-submitted related servers found.

    Related Servers

    • TradingView MCP Bridge

      allisonbit
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables 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.
      75 npm
      -

    • TradingView MCP Jackson

      Amit-fs
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to interact with TradingView Desktop via Chrome DevTools Protocol for automated morning briefs, chart analysis, Pine script development, and trading workflows.
      75 npm
      -

    • tv-cdp-mcp

      pbajkovic-hub
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents and terminals to control TradingView Desktop over the Chrome DevTools Protocol, providing 29 tools for reading charts and indicator values, exporting data to CSV, managing alerts and layouts, and paper trading.
      29
      MIT

    • TradingView MCP Bridge

      rajmaurya0904
      F
      license
      Not graded
      quality
      D
      maintenance
      Connects AI assistants to TradingView Desktop for chart analysis, Pine Script development, and workflow automation via Chrome DevTools Protocol.
      75 npm
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 6 tools

    Disambiguation4/5

    Each tool targets a distinct surface—screening, TA ratings, symbol lookup, install diagnostics, provider health, and OHLCV data—so most are unambiguous. The two diagnostic tools have some overlap around environment/credential health but are separated by install prerequisites versus current data-feed availability.

    Naming Consistency3/5

    All names share a tv_ prefix and snake_case, but the internal pattern is mixed: action-style names like tv_screener_run and tv_data_get_bars sit beside noun-style names like tv_ta_summary, tv_symbol_search, tv_setup_doctor, and tv_data_providers_status. A consistent verb_noun or noun_verb pattern would make the set more predictable.

    Tool Count5/5

    Six tools is well-scoped for a TradingView-oriented data server: screening, symbol discovery, technical summaries, historical bars, and health diagnostics each have a home. No tool feels redundant, and the count is neither thin nor bloated.

    Completeness4/5

    Core workflows are covered: find symbols, screen/filter, get TA reads, and pull OHLCV bars, plus status and diagnostic tools. Minor gaps exist—such as no direct single-symbol quote tool separate from bars/screener and no explicit indicator-value fetch beyond the TA summary—but agents can work around these.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources