Foundation
Session rules with a risk cap and a demo check, an X-ray of every indicator on the chart, and a desk Claude builds and saves for you.
Claude Code connected to cTrader through its local MCP server can do much more than the usual examples. These prompts read three indicators, turn their lines into exact orders, trail the stop, take partial profit and write your journal. A free PDF, step by step, with the full setup.
cTrader's published prompts cover briefings, risk checks, scaling, reviews, screening and chart building. None of them lets Claude trade from an indicator's own plan. These do: Claude reads the indicator values through the MCP, checks them against your rules and places the order with the stop and target the indicator drew.
They also add what cTrader's AI flows don't have built in: a trailing stop, break-even after the first target and partial profit at each target, all built from tools the MCP server already offers.
Session rules with a risk cap and a demo check, an X-ray of every indicator on the chart, and a desk Claude builds and saves for you.
Claude reads the drawn entry, stop and target and places the exact order, sized to your risk; when price already ran, it waits with a limit order instead.
A trend gate that refuses trades against the SuperTrend, a trailing stop that follows its Trailing SL line, and an exit when the trend flips.
Only fresh A or B grade plans, a profit ladder that scales out at TP1 and TP2 and moves the stop, and a read of how the last ten plans ended.
A three-indicator vote, a three-timeframe consensus and a six-market scanner that ranks the freshest live signals.
A five-point pre-flight (session, news, spread, margin, rules), the plan drawn as a risk-reward block before you say go, and position size worked out in the open.
Break-even at 1R, a time stop, cTrader price alerts on the indicator's levels and a one-line emergency flatten.
A journal Claude writes to a file with what each indicator said at entry and exit, a rule-break audit and an end-of-day handover.
The PDF opens on the next page and arrives by email. Then one short email a day for 40 days, each about one of my cTrader indicators or cBots: what it does and how it works.
{
"mcpServers": {
"ctrader": {
"type": "http",
"url": "http://127.0.0.1:9876/mcp/"
}
}
}Start cTrader first, then open the folder in VS Code and type /mcp in Claude Code: ctrader must show as connected. Begin every prompt with Using the cTrader local MCP server, so Claude uses cTrader's tools and not a web search.
The book has the full output map of all three indicators.
One prompt that makes every later prompt safer: an account check, a risk cap, verified fills.
Using the cTrader local MCP server, set up this trading session before anything else.
1. Call get_balance and tell me the broker, the account currency, balance and equity. get_balance does not say whether the account is a demo, so ask me, and make no trading call until I have answered in words.
2. From now until I say "end session", apply these rules to every request: risk at most 1 % of equity per trade (stop distance x pip value x volume), and if even the smallest volume would risk more, say so and place nothing; at most 2 open positions; never move a stop loss away from the price; never open a trade when the spread is more than 15 % of the stop distance; every price you use comes from a tool call in this session, never from memory or a web search.
3. After every trading call, read get_positions or get_pending_orders again and show the stored entry, stop and target next to what you intended. If they differ, say so first.
4. Reply "Session rules active" and the rules in four lines.Claude turns Flintridge's drawn entry, stop and target into a correctly sized order.
Using the cTrader local MCP server, on the active XAUUSD H1 chart that carries Flintridge Trader Pro:
1. Read output 3 (Signal) with count 150 and find the most recent non-zero value: its side (+1 buy, -1 sell) and how many bars ago it printed.
2. Read outputs 1 (Entry line), 2 (SL line) and 0 (TP1 line) with count 1. If any of them errors, the plan is no longer drawn: stop and tell me.
3. Get the live quote (get_spot_prices) and the symbol details (pipSize, lotSize, minVolume, volumeStep).
4. Check: the signal is at most 3 bars old; price has not already covered more than 30 % of the way from Entry to TP1; the spread is under 15 % of the stop distance. If a check fails, say which and stop.
5. Size the trade to risk 1 % of equity on the distance from the current price to the SL line, rounded down to the volume step.
6. Place a market order on the signal's side with stopLossPips and takeProfitPips converted from the SL and TP1 prices at the current price, label "flintridge-ai".
7. Re-read get_positions and show the entry, stop and target next to Flintridge's lines, with the difference in pips.cTrader's AI flows have no trailing stop; this loop trails yours along Hyper Trend's own Trailing SL.
/loop 5m Using the cTrader local MCP server: for my open XAUUSD position (label flintridge-ai, or the single XAUUSD position), read Hyper Trend PRO output 6 (Trailing SL) with count 1 on the active XAUUSD chart. If it errors, change nothing. If it is a valid stop (below the bid for a buy, above the ask for a sell, at least 1.5 x the spread away) and it is better than the current stop (higher for a buy, lower for a sell), move the stop loss there with amend_position and keep the take profit exactly as it is. Never move the stop backwards. Report the old stop, the new stop and the pips now locked.Yes. Enter your email and the PDF opens on the next page; the same link arrives by email. After it I send one short email a day for 40 days, each about one of my cTrader tools, and you can unsubscribe from any of them in one click.
Claude Code in VS Code, connected to cTrader Desktop through cTrader's local MCP server. The prompts use plain MCP tools, so other MCP clients can run most of them; the repeating prompts use Claude Code's /loop command.
For the prompts that read them, yes: Flintridge Trader Pro, Hyper Trend PRO and Supreme Power House 1.1.0 or newer, all on the cTrader Store. The session rules, the pre-flight, position sizing, break-even, the time stop, flatten, the journal and the audit work on any chart.
Only if you tick Allow trading via MCP in cTrader. Keep Require confirmation for trading operations ticked as well: then cTrader shows you every order, amend and close in its own window and nothing is sent until you approve it.
No. The prompts are tools for your own decisions. No indicator predicts the market, an AI agent can misread a value, and trading carries risk of loss. Start on a demo account and check every result the prompts show you.
Any broker that offers cTrader Desktop 5.10 or newer. The examples use gold (XAUUSD) on H1; every prompt says where to change the symbol and the timeframe.