{
  "schema_version": "1.1",
  "id": "s9:https://github.com/tradesdontlie/tradingview-mcp",
  "slug": "tradingview-mcp-1qplbet",
  "url": "https://feed7.dev/p/tradingview-mcp-1qplbet",
  "title": "tradesdontlie/tradingview-mcp",
  "why_included": "This MCP server gives Claude Code local chart, Pine Script, alert, and screenshot controls through TradingView Desktop, but depends on undocumented internals and may conflict with platform terms.",
  "summary": "The project connects Claude Code to TradingView Desktop through an MCP server, local **CDP port 9222**, and **84 MCP tools**. It supports chart navigation, indicator reads, Pine Script iteration, drawings, alerts, replay, screenshots, layouts, and JSONL monitoring.",
  "practical_implication": "It is a useful reference for making a stateful Electron application legible to an agent: expose compact structured reads before screenshots, keep commands available through both MCP and CLI, and add explicit health checks and tool-selection guidance.",
  "agent_context": "The project connects Claude Code to TradingView Desktop through an MCP server, local **CDP port 9222**, and **84 MCP tools**. It supports chart navigation, indicator reads, Pine Script iteration, drawings, alerts, replay, screenshots, layouts, and JSONL monitoring.\n\nIt is a useful reference for making a stateful Electron application legible to an agent: expose compact structured reads before screenshots, keep commands available through both MCP and CLI, and add explicit health checks and tool-selection guidance.\n\nIt requires a valid TradingView subscription and deliberate debug-port activation. The integration uses undocumented internal interfaces that may break, cannot execute trades, and its programmatic data access may conflict with TradingView terms or market-data licenses.",
  "source": {
    "name": "GitHub",
    "url": "https://github.com/tradesdontlie/tradingview-mcp",
    "published_at": null
  },
  "source_class": "tool",
  "content_type": "GitHub Repo",
  "layer": "tools",
  "domains": [
    "coding",
    "data"
  ],
  "topics": [
    "coding-agents",
    "mcp",
    "computer-use"
  ],
  "verification": {
    "status": "needs_review",
    "label": "Needs Review",
    "method": "unverified",
    "verified_at": null
  },
  "uncertainty": [
    "It requires a valid TradingView subscription and deliberate debug-port activation. The integration uses undocumented internal interfaces that may break, cannot execute trades, and its programmatic data access may conflict with TradingView terms or market-data licenses."
  ],
  "connected_context": {
    "meaning": "TradingView MCP makes a stateful desktop application agent-readable through compact structured operations, CLI parity, health checks, and selective screenshots. It specializes the browser-control pattern into a deep application harness, but also exposes a sharper adoption boundary: useful automation depends on a debug port, undocumented internals, subscription access, and acceptable terms and data-license use, while trade execution remains out of scope.",
    "corpus_size": 812,
    "generated_at": "2026-09-19T09:05:18.698Z",
    "connections": [
      {
        "title": "ChromeDevTools/chrome-devtools-mcp",
        "source_name": "GitHub",
        "source_url": "https://github.com/ChromeDevTools/chrome-devtools-mcp",
        "feed7_url": "https://feed7.dev/p/chrome-devtools-mcp-0ow49x2",
        "reason": "Both use DevTools access to turn live application state into an agent feedback loop; TradingView MCP specializes that general browser interface into domain-specific reads and actions for an Electron application."
      },
      {
        "title": "citrolabs/ego-lite",
        "source_name": "GitHub",
        "source_url": "https://github.com/citrolabs/ego-lite",
        "feed7_url": "https://feed7.dev/p/ego-lite-1i7kk2j",
        "reason": "ego lite emphasizes isolated authenticated browser sessions, whereas TradingView MCP attaches through an explicitly enabled local debug port, making session exposure and process isolation separate controls implementers must address."
      },
      {
        "title": "Full Workshop: Setting Yourself Up for Success —Jason Liu, OpenAI Codex",
        "source_name": "AI Engineer",
        "source_url": "https://www.youtube.com/watch?v=il1c1a2FufU",
        "feed7_url": "https://feed7.dev/p/full-workshop-setting-yourself-up-for-success-jason-liu-openai-codex-13uegzi",
        "reason": "The workshop’s requirement for explicit computer-use boundaries applies directly here because the integration can manipulate charts, scripts, alerts, and layouts even though it cannot execute trades."
      }
    ]
  },
  "lifecycle": "Current",
  "published_at": null,
  "modified_at": null,
  "supersedes": [],
  "expires_at": null,
  "formats": {
    "html": "https://feed7.dev/p/tradingview-mcp-1qplbet",
    "json": "https://feed7.dev/p/tradingview-mcp-1qplbet.json",
    "markdown": "https://feed7.dev/p/tradingview-mcp-1qplbet.md"
  }
}