Skip to main content
Glama
ezydubs

tradingview-mcp

by ezydubs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to tradingview-mcp

No user-submitted related servers found.

    Related Servers

    • TradingView MCP Bridge

      thinhbv
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to interact with TradingView Desktop charts for analysis, Pine Script development, and workflow automation via Chrome DevTools Protocol.
      75 npm
      -

    • tradingview-mcp

      bv2026
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to interact with TradingView Desktop charts via Chrome DevTools Protocol, supporting chart analysis, Pine Script development, drawing, alerts, and replay automation.
      75 npm
      -

    • TradingView MCP Bridge

      gitcyberclouds
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables 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.
      75 npm
      1
      -

    • TradingView MCP Bridge

      Abhiroy17
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to interact with locally running 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

    B3.2/5.0

    Scored across 97 tools

    Disambiguation3/5

    Although tools are grouped by domain, several boundaries overlap: chart_manage_indicator vs indicator_add, chart_set_visible_range vs chart_scroll_to_date, and ui_open_panel vs open_panel can lead to misselection. With 97 tools, the sheer number of similar state, indicator, and panel operations makes it hard for an agent to pick the intended one without reading descriptions closely.

    Naming Consistency3/5

    The tools generally use readable snake_case domain prefixes like chart_, pine_, draw_, replay_, and ui_, but the verb/noun ordering is inconsistent: data_get_ohlcv and depth_get coexist with symbol_info, get_status, and open_panel. Overall it is navigable, but the convention is mixed rather than uniform.

    Tool Count1/5

    97 tools is far above the 50+ threshold and creates an extreme selection burden for agents, even though the server covers a broad desktop-automation domain. The count itself is a major usability problem for MCP tool discovery and routing.

    Completeness5/5

    For its stated purpose, the tool surface is very complete: charting, Pine scripting, data extraction, drawings, alerts, replay, watchlist, UI automation, layouts/tabs/panes, and broker trading all have solid lifecycle coverage. Minor omissions like alert modification or drawing-property updates are easily worked around, and there are no obvious dead-end operations.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources