Back to directory

TradingView MCP Bridge

An unofficial MCP bridge that connects Claude Code to a locally running TradingView Desktop app over Chrome DevTools Protocol for chart analysis and Pine Script work.

TradingView MCP Bridge

TradingView MCP Bridge lets an AI agent read from and interact with a user's own already-running, already-licensed TradingView Desktop application through the Chrome DevTools Protocol, the same debugging interface built into every Chromium and Electron application. It does not connect to TradingView's servers, store or transmit market data, or bypass any paywall or access control; the debug port is disabled unless the user explicitly enables it with a standard Chromium flag.

The project frames itself as exploring a research question about how structured tool APIs can bridge language models and a stateful desktop financial application, including the latency, context, and reliability constraints that appear when an agent operates on live chart data. It is not affiliated with or endorsed by TradingView, and it relies on an undocumented internal API that can change without notice.

It is written in JavaScript and requires a valid TradingView subscription and the TradingView Desktop app.

More in MCP servers

See all 734
  • Light Cloud

    light-cloud.com

    A hosting platform that deploys a static site, a container, or a managed Postgres database straight from a GitHub, GitLab, or Bitbucket push, with a preview URL for every branch and an MCP server for deploying from Claude Code.

  • ForensicDbg

    forensicdbg.com

    A post-mortem debugger for native Windows x86 and x64 crashes, with an MCP interface so AI tools can consume crash-dump analysis directly.

  • Karada.ai

    karada.ai

    A CI/CD platform that auto-compiles existing APIs into Go MCP servers, attaches composable middleware, and exposes them through one gateway usable from Cursor, Claude Code, and Windsurf.