Skip to content

Pine Script Indicators

Overview

Seven custom ICT-methodology indicators being rebuilt from scratch. Each indicator generates data points that flow through TradingView → MCP → system. The goal is clean, consistent, integration-ready outputs.

Status: Documentation phase. No code yet.

Current Indicator Set

1. FVG + OB + MSS (Combined)

  • Purpose: Fair Value Gaps, Order Blocks, and Market Structure Shifts in one open-source indicator
  • Timeframes: All
  • Status: To be documented

2. Next Candle Bias

  • Purpose: Candle bias model for directional prediction
  • Timeframes: All
  • Status: To be documented

3. SMT (Smart Money Technique)

  • Purpose: Smart money divergence signals between correlated pairs
  • Timeframes: All
  • Status: To be documented

4. Session Bias

  • Purpose: Intraday session directional bias
  • Timeframes: Intraday
  • Status: To be documented

5. Macro

  • Purpose: Macro timing windows
  • Timeframes: Intraday
  • Status: To be documented

6. Economic Calendar

  • Purpose: News and event data source
  • Note: Treated as an indicator/script data source — data flows from TradingView into MCP and then into the system
  • Timeframes: Intraday
  • Status: To be documented

7. EMA

  • Purpose: Trend following via exponential moving averages
  • Timeframes: Daily+
  • Status: To be documented

How MCP Will Read Indicators

Pine Script indicators produce visual elements that MCP tools extract:

Pine Graphic MCP Tool What It Reads
line.new() data_get_pine_lines Price levels, support/resistance
label.new() data_get_pine_labels Signal text + price
box.new() data_get_pine_boxes Zones (high/low ranges)
table.new() data_get_pine_tables Structured data (bias state, stats)

Each indicator's documentation will specify which visual channels it uses and what data each element carries.

Build Order

  1. Document each indicator (what it does, what it outputs)
  2. Build or adapt each indicator in Pine Script
  3. Standardise outputs across all indicators
  4. Connect through TradingView MCP
  5. Build UI mock
  6. Feed real indicator data into UI
  7. Validate everything end-to-end