Quantum can be driven from outside by an AI client — Claude Code, Claude Desktop, or anything else that speaks MCP. It offers 151 tools over a local connection: the layout, the charts and everything they draw, drawings, strategies and backtests, the replay, your watchlists, scans and alerts, your stored market data, and orders. This page is generated from the server's own tool list. For writing strategies inside Quantum, see the strategy guide.
Connecting
The server is off until you turn it on, listens on your own computer only, and answers nothing without the token from AI Control → ACCESS. That screen has the command ready to copy, shows which clients are connected, and logs the calls they make. Regenerating the token disconnects whatever was using the old one.
Anything holding it can drive Quantum on your machine, within the switches you have turned on. Keep it out of shared configs and screenshots, and regenerate it if it leaks.
What each switch opens
Tools are gated in groups, each with its own switch in AI Control. A tool whose group is off refuses and says so.
Switch
Tools
What a client can do
Layout
28
Arrange Tabs, Panes and Windows. Workspaces, tabs, panes and windows, the Analyzer window, and the app's theme.
Charts
30
Read Charts and Change Indicators. Bars, the footprint, market structure, the profiles and their desks, levels, measured moves, Simple Momentum; add and tune indicators; scroll, zoom and screenshot.
Drawings
5
Draw on Charts. Trend lines, rays, rectangles, fibs, text, channels, anchored VWAP, risk/reward and volume profiles.
Strategies
21
Write and Backtest Strategies. Read and write strategy files, compile them, run and cancel backtests, read results, and drive the parameter workbench and the Analyzer — a sweep is a backtest.
Replay
15
Control Replay. List, download and prepare sessions; play, pause, seek and set the speed.
Stored data
14
Read Stored Market Data. SELECTs against your captured ticks, the order book and the DOM stats strip, the indicator registry, and where the recorded order flow has holes.
Feeds
3
Fetch and Repair Market Data. Asking NinjaTrader to download history, and repairing the store from it. Separated from reading because fetching is not reading — data_coverage stays under Stored data, but its fill and fetch arguments ask for this switch from inside the tool.
Journal
2
Read and Drive the Trade Journal. What the journal is showing — the range, the filters, the trade count and net — and the controls to change it. Your own fills, so it is switched separately from market data.
Alerts
8
Write Alert Rules. Read the firing record, and add, edit or delete rules. alerts_test makes a toast and a sound on your desk.
Scans
7
Write Saved Scans. Run a scan, and create, change or delete your saved ones — including which one is filtering the watchlist.
Desk
7
Change Watchlists and the AI Loop. Edit watchlists, switch which one the panels show, and arm or disarm the AI watch loop.
Web
1
Fetch Web Pages. Fetches a public page, asking you once per site. It never reaches addresses on your own machine or network.
Trading
9
Trade (under the rules). Read the trading state, place and cancel orders, flatten, and arm or disarm strategies — every one of them gated again below.
The italics are how each switch reads in the panel, under Clients May. The plain name is what a refusal calls it.
The one tool no switch covers
app_info — the handshake: version, build, and nothing else. It answers whenever the server is on and the token is right, by design, because a client has to be able to connect before it can be told that anything else is denied.
Everything else belongs to a switch, and anything that does not is refused rather than allowed. A tool Quantum has not assigned to a group comes back saying so and naming it as a bug in the app — not something you can switch on. That is the safe direction to fail: a family nobody grouped shows up as a tool that plainly does not work, the first time it is called, instead of a switch you turned off that was quietly covering nothing.
On builds before 1.0.27, the switches covered less
A switch is matched by the first word of a tool's name, and the rule for a name that matches nothing is allow. The families added after the original seven switches — alerts, scans, watchlists, the AI watch loop and the feed tools — matched none of them, so they answered with every switch off. That is closed now and each has its own switch. On an older build, treat the switches as covering charts, drawings, layout, strategies, replay, stored data and trading only.
What needs your approval
Anything that could move money stops at a confirmation window inside Quantum. The client asks; you decide.
A confirmation window opens and waits for you. It blocks the app, has no default button, ignores clicks for a moment, and shows a live account in red. Walking away is a refusal.
position_flatten, position_close_size
The same window. Risk-reducing actions are the ones your rules can let through automatically.
strategy_arm, strategy_disarm
Arming is an order-affecting action and is gated the same way.
Your AI trading rules
Off until you switch them on, account by account, with limits on contracts, risk per order, daily loss, order count and trading hours. Anything outside them comes back to you.
STOP ALL
Your button, not a tool: it turns AI trading off, disarms strategies, cancels orders and flattens. No tool can press it or change your limits.
db_query
Read-only: the capture is opened read-only by the driver, and only SELECT (or WITH … SELECT) is accepted.
data_coverage with fill or fetch
The exception to that: it imports .qtape files and re-seeds the ladder, and no switch gates it. Nothing is deleted and imported prints are stamped historical, so they stay tellable apart from live ones.
Live orders need both indicator licenses. On the subscription and the trial, orders route to the replay simulator.
Reading what the chart draws
The newest tools answer with the numbers behind the picture, computed by the app itself — so an analysis reads the same verdict the pane draws rather than a second implementation of the rule.
Chart readers
// What the pane draws, as numbers — no re-deriving the rulechart_levels// every level line: VWAP, session levels, prior day, IB, fibschart_volume_profile// the profile behind the chart: POC, value area, rowschart_fvg// fair value gaps with their fill and mitigation statechart_ssl// the SSL ribbon: line, channel and state per barchart_footprint_footer// every footer cell, as drawn AND as a numberchart_footprint_signals// FIOrderFlow's 25 named bar signals, bar by barchart_measured_moves// impulse, fib trigger, -23.6% target, target/stop hitchart_tpo// the market profile: POC, value area, IB, tails,// poor extremes, single printschart_volume_profile// volume at price, session by session// Both profiles can be cut at the desks instead of the day:chart_tpo { "session": "global" } // asia, london, newyorkchart_volume_profile { "session": "global" } // the same three, by volume// And when the footprint goes quiet, the reason is a tool, not a guess:data_coverage// per day: prints stored, the window, every gap
Watching and scanning
Newer than the readers, and a different kind of thing: these do not answer a question once, they leave something running on your desk.
Family
What it leaves behind
Alerts
A rule is source / operator / source — a break of structure on a timeframe, a change of character, a price crossing a level, a stacked imbalance. alerts_add creates one, alerts_stream reads what has fired, and alerts_test fires the toast and the sound so you can check you will notice it.
Scans
A scan is an AND of conditions over a watchlist. scans_run is a snapshot — it also returns the symbols that failed and which condition they failed on. scans_filter is the live one: the watchlist then shows only what passes, and follows the market.
Watchlists
watchlist_add and watchlist_remove edit them exactly as you would, and watchlist_select changes which one the panels are showing.
The AI watch loop
ai_loop_start arms the AI panel to re-ask one question on a trigger as the market moves, rather than answering once. It shows as the WATCH card in the panel, and ai_loop_stop disarms it.
None of these four is behind a switch. They are also the tools whose effects outlive the call, which is the pairing worth knowing about.
Querying stored data
Quantum keeps what it records in SQLite. db_schema describes the tables and their units; db_query runs one SELECT against them. The tick table holds tens of millions of rows, so filter on the instrument and a time range and let SQL do the aggregating.
Stored data
// db_schema first: it names the tables, columns and units.db_query {
"sql": "SELECTinstrument, COUNT(*) ASprintsFROMtick \
WHEREinstrument = 'MNQ 12-26'ANDtsNsBETWEEN ? AND ? \
GROUPBYinstrument",
"database": "live",
"max_rows": 200
}
// Shaped readers, when you do not want to write SQL:db_heatmap// resting size over time, as the heatmap drew itdb_dom_volume// volume at price from the book's own recorddb_trades// the prints themselves
Every tool
151 tools · click one for its arguments
Futures trading involves substantial risk of loss. This page documents a programmatic interface to your own copy of Quantum; it is not trading advice. An AI client driving a trading application can place orders you did not intend — keep the trading switch off unless you want it, and test on a replay session first. See our full disclaimer.
