Skip to main content
Glama
pbajkovic-hub

tv-cdp-mcp

by pbajkovic-hub
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to tv-cdp-mcp

No user-submitted related servers found.

    Related Servers

    • tradingview-mcp

      bv2026
      F
      license
      Not graded
      quality
      B
      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.
      99 npm
      -

    • 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.
      99 npm
      -

    • TradingView MCP Bridge

      Abhiroy17
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to interact with locally running TradingView Desktop for chart analysis, Pine Script development, and workflow automation via Chrome DevTools Protocol.
      99 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/5.0

    Scored across 29 tools

    Disambiguation5/5

    Every tool targets a distinct resource and action—alerts, layouts, chart state, studies, and trading each have clear boundaries. Even similar-sounding tools like tv_list_alerts vs tv_get_alert or tv_list_layouts vs tv_list_saved_layouts are unambiguously separated by read scope and detail.

    Naming Consistency4/5

    The dominant pattern is tv_verb_noun in snake_case (list_alerts, set_symbol, delete_layout), which is consistent and predictable. Minor deviations include tv_screenshot, tv_study_template (noun with action parameter), and tv_trading_status, but these do not undermine the overall pattern.

    Tool Count4/5

    29 tools is on the higher end for an MCP server, but the server covers five distinct domains (alerts, layouts, chart, studies, trading), and each tool has a distinct role. The count feels justified rather than bloated, though it is close to the upper bound of what is appropriate.

    Completeness4/5

    The surface is nearly complete for the stated scope: full CRUD for alerts and layouts, chart inspection and mutation, study input management, template lifecycle, and paper trading operations. Minor gaps exist—such as no way to remove a single study from a chart or modify an existing order's price/size—but agents can work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources