Repository Setup¶
The ICT Edge Fund platform is split across four independent Git repositories, all housed under a single TradingDesk/ workspace folder.
Folder Structure¶
TradingDesk/
├── tradingview-mcp/ # MCP server — 78 tools for TradingView Desktop
├── tradingview-strategy/ # Strategy layer + dashboard + Docker deployment
├── ictedge-mcp/ # Window focus utility
└── docs/ # MkDocs wiki — this site
Each repository is a standalone Git repo. There are no Git submodules or monorepo tooling involved.
Inter-Repo Dependency¶
tradingview-strategy depends on tradingview-mcp via a local file reference in its package.json:
Running npm install inside tradingview-strategy creates a symlink automatically. This means:
- Both repos must be cloned as siblings in the same parent folder.
- Changes to
tradingview-mcpsource files are picked up immediately -- no reinstall required. - There is no need to run
npm linkmanually.
Key Files Per Repo¶
tradingview-mcp¶
| Path | Purpose |
|---|---|
src/server.js |
MCP server entry point |
src/core/ |
Tool implementations (78 tools) |
src/cli/ |
CLI interface for running tools directly |
tradingview-strategy¶
| Path | Purpose |
|---|---|
src/scan.js |
Full scan pipeline (readers, interpreters, engine) |
dashboard/server.js |
Web dashboard server (port 8000) |
docker-compose.yml |
Production deployment configuration |
ictedge-mcp¶
| Path | Purpose |
|---|---|
src/server.js |
MCP server entry point |
scripts/launch_tv_debug.* |
TradingView CDP launcher scripts (VBS/shell) |
docs¶
| Path | Purpose |
|---|---|
mkdocs.yml |
MkDocs Material site configuration |
docs/ |
Markdown content for the wiki |
Running Tests¶
The test suite lives in tradingview-strategy and covers all interpreters and the strategy engine:
There are currently 63 tests across the suite. All tests use the Node.js built-in test runner (no external test framework required).
Development Workflow¶
- Make changes in
tradingview-mcportradingview-strategy. - Run the test suite to verify nothing is broken.
- Restart the dashboard server if you changed server-side code:
- For docs changes, run MkDocs locally:
Then open
http://localhost:8001to preview.