Skill Reference
Beta, pre-release. The NinjaTrader MCP server and its trading skills are in beta and aren’t yet generally available. The beta runs on Demo only, which trades simulated money. Live access opens later. Server hostnames, the tool set, the skills, and the onboarding flow may change before launch.
Each skill routes on natural language—you never invoke one by name. The phrases below are examples of what triggers each skill. Anything close routes the same way. Every skill leaves execution decisions to you. See Trading Skills for details. The Tools column lists the primary MCP tools each skill uses. Skills also call user_profile to discover your accounts when the conversation hasn’t named one.
Pre-trade
contract-intel resolves the exact symbol the other skills need, so bare product codes route through it first. pretrade-risk handles initial entry sizing—to change a position you already have, use scale-manager. And risk-coach answers “is this a good trade?” with behavioral context from your own history, not a yes/no verdict.
Live position
A bare positions request routes to position-watchdog—charting requests go to chart-render only when you ask for a chart. alerts-composer is also the submission path for alert expressions proposed by position-watchdog, event-watch, and pretrade-risk. For same-underlying pairs like ES and MES, use contract-intel rather than correlation-hedge. And when you approve a hedge and want it placed, scale-manager proposes the payloads.
Post-trade
The three review skills split by question. trade-journal is descriptive: what happened today. trade-debrief is prescriptive: what should change. trade-replay is single-trade counterfactuals: what if that trade had gone differently. trade-replay isn’t backtesting—it replays your actual fills, not a strategy over market history.
Visualization
chart-render draws data the other skills produce: bars and fills directly from the tools, plus analytics from market-context and round-trip trades from trade-journal when a chart needs them.

