Skip to main content
AskFutures exposes one programmatic surface: an MCP server. Connect any MCP-capable client — Claude Code, Cursor, Codex, or your own — and you get the same assistant you’d use in chat, available as a set of tools your agent can call directly.
The MCP server is the only public way to drive AskFutures from code. Under the hood it runs the exact same strategy engine, deterministic backtester, and optimizer as the web app — so the numbers match, byte for byte.

​
Why use it

Stay in your editor

Build and backtest futures strategies from Claude Code, Cursor, or Codex without leaving the tool you already work in.

Automate the loop

Script the describe → backtest → optimize → compare cycle. Generate a batch of variations, run them, and read the results programmatically.

Same trustworthy engine

Tools call the same deterministic backtester as the app. Same rules and data always produce the same numbers — the AI never invents performance figures.

​
What you can do

You describe strategies in plain English, just like in chat — the MCP tools handle the rest:
  • Create a strategy from a plain-English description (a market plus entry, exit, filters, and parameters).
  • Backtest it on years of real CME Group data, net of modeled slippage and commission.
  • Optimize — sweep parameter ranges to find better-performing settings.
  • Iterate — refine an existing strategy, version it, and compare runs.
  • Inspect strategies, sessions, and reference data (symbols, contract specs).
For the full list, see the MCP tools reference.

​
The async model: create → wait → optimize

The one thing to internalize before you write any code: the heavy work is asynchronous. Building a strategy and running a backtest can take a while — the engine is replaying years of minute-level history bar by bar. So those tools don’t block. They start a job and hand you back a task you poll until it’s done.
1

Kick off the work

Call a tool like create a strategy or run an optimization. It returns immediately with a task to track — not the finished result.
2

Wait for completion

Poll the wait-for-completion tool with that task until the job finishes. A good agent does this in a loop, surfacing progress as it goes.
3

Read the results

Once complete, you get the strategy card and backtest metrics — P&L, win rate, drawdown, and the full trade list — ready to inspect or feed into the next step.
4

Iterate or optimize

Refine the rules, sweep a parameter range, or compare versions. Each of these is another create → wait cycle.
Most MCP clients (Claude Code, Cursor, Codex) handle the polling loop for you — the agent calls the wait tool on its own. You mostly just describe what you want.
Backtest and optimization results are hypothetical and simulated, net of modeled slippage and commission. Past performance does not guarantee future results. Always test before you trade.

​
Before you start

You need MCP access enabled on your account. There’s no self-serve toggle yet — see Authentication for how to request it and how sign-in works.

​
Next steps

Quickstart

Connect Claude Code, Cursor, or Codex in a couple of minutes.

Authentication

Sign-in flow, token lifetimes, and getting access enabled.

MCP tools

Every tool, what it does, and what it returns.