MCP server for trading: AI client to live MT5
The Model Context Protocol gave AI agents a safe way to call real tools - and trading is the most obvious place that matters. This guide explains what a trading MCP server is, what already exists (honestly), and how to connect an AI client to a live MetaTrader account with receipts and a dry-run default, step by step.
Quick answer
SIXTY WORDS, NO SCROLLING.
Quick answer: an MCP server for trading is a bridge that lets AI applications call trading tools - read positions, submit signals, check receipts - through the open Model Context Protocol instead of hand-pasting numbers. SignalForge ships one for MT4/MT5 with scoped keys and dry-run by default, included from the Trader plan at $14.99/mo. Checked October 31, 2026.
What an MCP server is
PLAIN ENGLISH FIRST, PROTOCOL SECOND.
The one-sentence version
MCP (Model Context Protocol) is an open standard that lets an AI application call external tools in a controlled way: the server declares what it can do, the client picks which tools to expose, and every call is a typed request with a response - not a prompt hoping for the best. Think of it as USB for AI tools: one plug, any device, permissions enforced at the port.
Why it appeared in 2025
Before MCP, every AI-plus-anything integration was bespoke glue: a script here, a scraper there, an API key pasted into a prompt. It worked for demos and broke in production. MCP standardized the contract, and by 2026 the major AI clients support it natively - which means a trading MCP server works with the assistant you already use, no custom code.
What it changes for trading
A trading agent without MCP reads a screenshot, guesses the numbers and hand-writes an order. With MCP it calls read recent signals, gets typed data, decides, calls submit signal with dry-run, and reads a receipt with a signal id. The difference is not intelligence - it is that the agent can no longer imagine an execution. It either has a receipt or it does not.
The MCP-for-trading landscape, honestly
THIS NICHE IS WEEKS OLD. THAT IS THE OPPORTUNITY.
Connect an AI client to MT5 in four steps
READ FIRST, TRADE LAST.
Create a read key
In your dashboard, under SFConnect: create an API key with read scope. Nothing it can do moves money. Two minutes, zero risk
Add the MCP server
Point your AI client (Claude Desktop, Cursor, or any MCP-capable app) at the SFConnect MCP endpoint, authenticating with the key. Standard MCP config
Read before trading
Ask the agent to pull your recent signals and their receipts. This is the loop that replaces screenshots: typed data, ids, decisions with reasons. Verify it matches your dashboard
Dry-run, then trade
Have the agent submit a signal with dry-run and read the receipt. When a week of dry-runs looks right, create a read+trade key - or stay read-only forever. Live is a scope, not a default
The full tool list, auth and configuration: api.signalforge-ai.com/docs/api - and the SFConnect overview covers keys and scopes in one page.
What a session actually looks like
THE DIALOGUE, WITH RECEIPTS.
You: check my last 5 signals and their outcome
Agent: (calls recent_signals) 4 executed, 1 rejected - XAUUSD buy rejected:
"stop loss inside spread" at 14:02 UTC. Receipts s-8812..s-8816.
You: ok, buy 0.01 EURUSD, stop 50, target 100 - dry run first
Agent: (calls send_signal dry_run) Receipt s-8817: validated, sized 0.01,
NOT placed (dry-run). Ready to go live when you are.Notice what the agent cannot do: invent a fill. Every claim traces to a receipt id. That single property is what makes an AI trading agent auditable instead of a story.
Guardrails that matter in any trading MCP
CHECKLIST BEFORE YOU CONNECT ANY SERVER.
- Dry-run by default. The server should run the full path - validation, sizing, filters - without placing orders until you explicitly go live.
- Read and trade as separate scopes. A key that only reads cannot lose money, even if it leaks.
- A receipt for every action. Submissions, rejections, reasons. If the agent's actions are not journaled server-side, you are flying blind.
- No broker credentials inside the loop. Your MT5 stays yours; the server routes through your own terminal setup, not through your password.
- Instant revocation. One click, key dead, agent disarmed.
FAQ
THE FIVE QUESTIONS THIS GUIDE GETS.
Do I need to code to use a trading MCP server?+
Which AI clients work with MCP?+
Can the agent place live trades?+
Does it work with MT4 and MT5?+
What does it cost?+
FROM DRY-RUN TO LIVE, IN YOUR CONTROL
Create a key, connect your AI client, run dry for a week.
INCLUDED FROM $14.99/MO (TRADER) · 14-DAY FREE TRIAL · DRY-RUN BY DEFAULT