User guideAI trading with MCP

Connections & settings / 8 min read

AI trading with MCP

Ask in plain language. Review the next step in LunaBot.

In LunaBotSettings → Connected apps
On this page

Start with your own words

LunaBot connects a compatible assistant to your trading workstation through MCP. You type into the assistant you already use. LunaBot provides the permitted account information and trading tools.

You do not need to write code. You do need a Windows computer, LunaBot, an MCP-compatible client and a Paper or MT5 Demo account to practise. The assistant may require its own subscription or model access.

Try the interactive example to see the workflow before connecting anything.

Connect in four steps

  1. In LunaBot, open Settings → Connected apps → Connect assistant. Choose Codex, Claude Desktop, Claude Code or Other.
  2. Select your Paper or Demo account. Start with Account records; add Research jobs if needed.
  3. Create the connection and follow its configuration instructions. Restart the client if it needs to load the new settings.
  4. Ask the assistant to read your account status. Confirm a real request appears in LunaBot’s connection activity.

Installing a model alone is not enough: its client must support the MCP connection. See Connected apps for configuration and troubleshooting.

Your first request

Read my shared Demo account in LunaBot. Tell me whether it is connected, what trades are open and whether monitoring is running. Do not change anything.

Check that the response names the account you intended. If it cannot access the account, review the shared accounts, permissions and connection state in LunaBot.

From a request to a trade

  1. Ask for a setup. Name the market and account. Ask the assistant to use available current data and saved limits, and explain when it would choose no trade.
  2. Prepare it in LunaBot. A permitted assistant can submit a Scout or preview a protected manual order. A description in chat is not an order.
  3. Review the terms. Inspect the market, side, size, stop, target, costs and estimated risk. Ask for missing details.
  4. Approve when appropriate. In Review mode, eligible proposals wait for approval. Manual submission requires its separate permission and exact preview. LunaBot rechecks the request at submission.
  5. Check the result. Confirm the broker response and resulting position or pending order. A request may be rejected, expire or require reconciliation.

Automatic Scout handling requires compatible account mode, Scout policy and execution permissions. Live use also needs Live activation. Grant these deliberately after you understand the Demo workflow.

Requests you can copy

Start the day

Permissions: Account records

Read my shared Demo account in LunaBot. Summarise connection status, balance, equity, open trades, pending orders and strategy activity. Flag stale prices or missing data. Make no changes.

Research EUR/USD

Permissions: Account records · Research jobs

Review EUR/USD on my shared Demo account. Check available bars and trading costs. Compare the existing strategies using the same dates and assumptions. Explain drawdown, trade count and limitations. Say if there is too little data to choose. Do not activate a strategy or trade.

Prepare a Scout

Permissions: Account records · Trade proposals

Find an EUR/USD setup to review on my Demo account using current available data and my saved limits. Explain entry, stop, target, costs, risk and when the idea becomes invalid. If no setup qualifies, say no trade. Submit a Scout only if my connection has permission; leave execution for my review.

Build a strategy draft

Permissions: Account records · Draft strategies

Create a disabled EUR/USD strategy draft using a supported LunaBot strategy type. Explain the timeframe, every parameter, filters, stop and target rules. Use my broker’s exact symbol. Identify any unsupported rule instead of inventing it. Leave the draft inactive for me to review.

Preview an order

Permissions: Account records · Manual preview

Help me prepare a protected EUR/USD market order on my Demo account. Ask for any missing side, size, stop or target. Preview the exact order in LunaBot and explain the estimated risk and costs. Do not submit it; show me what I would be approving.

Review my trading

Permissions: Account records · Investigations when needed

Review this week’s completed trades on my shared account. Show net results, costs, losses and performance by strategy where available. Explain rejected orders using the recorded reason. Separate facts from guesses and tell me where records are missing. Do not change trades or settings.

Open the prompt library with Copy buttons →

Know what to expect

An assistant can help explain and operate supported tools. It cannot guarantee profit, manufacture missing market data or make an unsupported strategy run. Research results depend on history, costs and assumptions.

You may choose any compatible client and supported model, but tool use and reasoning quality differ. Ask the assistant to show actual LunaBot results and say when data is missing. It is reasonable for a session to end with no trade.

LunaBot checks permissions, account and strategy limits, quote freshness, broker rules and applicable licence state. Start in Paper or Demo while learning position sizing, stop loss and order approval.

Stay in control

In Connected apps, change the accounts and actions a client may access, inspect its activity or revoke it. Saving changed permissions rotates access and requires reconnecting the client.

Use Pause new entries to stop new entries while broker sync and existing-position management continue. Full monitoring pause follows your managed-MT5 preference and can also stop local management. Broker-held stops and targets remain at the broker.

Never paste connection credentials or broker passwords into a public conversation. For assistance, email luneya17@gmail.com.

Product image

LunaBot interface · demonstration setup