ICT Edge Fund¶
AI-powered trading platform reading ICT concepts from TradingView.
ICT Edge Fund connects to TradingView Desktop via Chrome DevTools Protocol, reads four custom Pine Script indicators implementing ICT methodology, interprets their graphics into structured signals, and displays live trade readiness on a web dashboard.
Three-Repo Architecture¶
graph LR
TV["TradingView Desktop"] -- CDP 9222 --> MCP["tradingview-mcp"]
MCP -- "78 tools" --> STR["tradingview-strategy"]
STR -- "StrategyFlags JSON" --> DASH["Dashboard :8000"]
ICT["ictedge-mcp"] -. "focus + launch" .-> TV
| Repository | Role |
|---|---|
| tradingview-mcp | 78-tool MCP server. Connects to TradingView Desktop via CDP. 2 runtime dependencies. Exposes every chart interaction as a typed tool. |
| tradingview-strategy | ICT strategy interpretation layer. Reads 4 Pine indicators through MCP, runs readers/interpreters/engine pipeline, produces StrategyFlags JSON. Serves the live dashboard. |
| ictedge-mcp | Window focus utility with launch scripts. Starts TradingView Desktop with CDP enabled on port 9222. |
What Each Component Does¶
tradingview-mcp -- The interface layer. It speaks Chrome DevTools Protocol to TradingView Desktop and wraps 78 operations (chart control, Pine graphics reading, screenshots, alerts, replay) into MCP tools with Zod-validated schemas. The strategy layer uses 6 of these tools.
tradingview-strategy -- The brain. Five readers pull indicator data in parallel. Five interpreters apply ICT contract rules (color mappings, spatial logic, label parsing) to produce typed signals. The engine scores confluence, applies no-trade filters, and builds the final StrategyFlags JSON. A built-in dashboard server exposes results at localhost:8000.
ictedge-mcp -- The launcher. Provides a focus-window tool and platform-specific scripts (.bat, .vbs, .sh) to start TradingView Desktop with --remote-debugging-port=9222, enabling the CDP connection that everything else depends on.
Dashboard -- Live web UI served by tradingview-strategy. Shows strategy signals, chart screenshots, and indicator settings. Proxied through nginx to ictedgefund.com.
Docker stack -- nginx reverse proxy (ports 80/443), MkDocs docs container, certbot SSL. Routes ictedgefund.com to the dashboard and docs.ictedgefund.com to this wiki.
Quick Links¶
Architecture¶
- System Overview -- full platform diagram and design principles
- tradingview-mcp -- 78-tool MCP server capabilities
- tradingview-strategy -- readers, interpreters, engine, dashboard
- Data Flow -- end-to-end walkthrough with concrete examples
- ictedge-mcp -- window focus and TradingView launcher
Getting Started¶
- Getting Started -- installation, setup, first run
Live Systems¶
- Dashboard -- web UI reference
- Deployment -- Docker, nginx, SSL, domains
Reference¶
- Indicator Contracts -- Pine indicator data formats
- Signal Schema -- StrategyFlags JSON reference
- Roadmap -- planned MCP servers and execution layer