Ask your AI about your real MT5.
SFConnect connects your AI assistant and your own code to your SignalForge AI account. Ask Claude or Cursor whether your EA is online or why a signal was rejected, or send orders from a Python script. Every order goes through your own webhook, with the same rules as a TradingView alert.
Your AI or your code.
One personal key, two doors. Both see only your data and both follow the same rules.
Ask in plain words
MCP is the open standard AI apps use to call tools. Add the SignalForge server to your AI app and it can read your accounts, EA status and signal history, and send a signal if your key allows it.
$ claude mcp add --transport http signalforge \ https://api.signalforge-ai.com/mcp \ --header "Authorization: Bearer sfk_..."
Or one HTTP call
Anything that can send an HTTPS request can trade your MT5: a Python bot, a Node script, a cron job. Bearer key in the header, JSON in the body, a receipt in the response.
import requests API = "https://api.signalforge-ai.com/api/v1" KEY = {"Authorization": "Bearer sfk_..."} # dry run by default: nothing is sent requests.post(API + "/signals", headers=KEY, json={"action": "buy", "symbol": "XAUUSD", "lot": 0.1})
Running in 3 steps.
All from your dashboard, under SFConnect. The page gives you the exact snippet for each app.
Create a key
A new key can read only. Tick Allow sending signals if you want it to trade. The key is shown once; we store only its hash, and you can revoke it in one click.
Plug it in
Claude: Settings → Connectors → Add custom connector. Claude Code: one claude mcp add command. Cursor and VS Code: a short mcp.json. Or put the key in your own script.
Ask, then send
Ask about your accounts and signals straight away. Signals start as a dry run: validated and previewed, nothing sent. Set dry_run to false when you are ready to go live.
Six tools for your AI.
Five only read. The sixth sends a signal, and only with a key that is allowed to.
Who you are
Your SignalForge user, plan and account dates, with the email masked.
Your MT5 accounts
Every account with its label and EA state: connected, version and SFCloud.
EA health
EA version, connection and last ping per account. Is it online right now?
Signal history
Your signals, newest first, up to 200 at a time. Filter by account or date.
One signal, in full
What happened to a signal and why: executed, or rejected with the exact reason.
Send a signal
Market, pending, close and modify orders to your EA. Dry run unless told otherwise.
Same rules as a TradingView alert.
A signal from SFConnect enters through your personal SignalForge webhook, the same door your alerts use. Nothing skips your settings.
- Your position sizing: risk %, fixed lot or the signal's lot, as your panel says.
- Your news and trend filters, and your symbol mapping.
- Prop Firm Shield checks your prop-firm limits on every signal.
- Your SignalForge EA, on SFCloud or on your own MT5. No account password is ever part of a call.
In our demo test, orders sent through the MCP server were executed in MT5 in 137 to 328 ms. Your broker and setup decide the figure you will see.
Safe by default.
An API that can trade needs brakes built in. These are on for every key, from the first call.
Dry run by default
A signal is only validated and previewed until you set dry_run to false. The same goes for your AI.
Read-only keys
New keys only read. Sending live orders needs a key with Allow sending signals ticked.
Only your data
A key sees your accounts and signals, nothing else. No billing, no passwords, no broker credentials.
Revoke in one click
A revoked key stops working at once. Keys are stored as a hash, never in plain text.
Built-in limits
60 requests and 10 signals per minute per key. A runaway loop can't flood your account.
No double orders
Retry with the same idempotency_key and the order is not sent twice within 24 hours.
The whole thing in 3 minutes.
Creating a key, connecting an AI app, asking about the account and sending a signal from code.
The full surface.
Base URL https://api.signalforge-ai.com. Auth with Authorization: Bearer sfk_... on every call.
| ENDPOINT | WHAT IT DOES |
|---|---|
| GET/api/v1/me | Your user, plan and account dates. |
| GET/api/v1/accounts | Your MT5 accounts with EA state and labels. |
| GET/api/v1/ea/status | EA version, connection and last ping per account. |
| GET/api/v1/signals | Signal history, newest first, filterable by account and date. |
| GET/api/v1/signals/{id} | One signal with its decision and reason. |
| POST/api/v1/signals | Send a signal. Dry run unless dry_run is false; optional idempotency_key. |
| POST/mcp | MCP server (Streamable HTTP, JSON-RPC 2.0) with the six tools. |
The fine print.
What SFConnect does today, and what it doesn't.
What it does
- Reads your accounts, EA status and signal history, and sends signals to your EA.
- Works with MetaTrader 5 through the SignalForge EA, on SFCloud or on your own MT5.
- Applies your sizing, filters and Prop Firm Shield to every signal, like any alert.
- Text from your alerts reaches your AI as data, not instructions.
What it doesn't
- MT4 is not supported. SFConnect works with MT5 only.
- No market data or charts. It reads your account, not prices.
- It won't trade on its own. Your EA must be running, and live orders need a key that allows them.
- Not in Starter. SFConnect comes with Trader, Pro and Elite.
Included from Trader.
SFConnect comes with Trader, Pro and Elite. Starter keeps the bridge and SFCopier.
- SFConnect: API + MCP server
- 3 MT5 accounts on the bridge
- Prop Firm Shield, news and trend filters
- Everything in Trader
- 5 MT5 accounts on the bridge
- 5 hosted MT5 terminals (SFCloud)
- Everything in Trader
- 10 MT5 accounts on the bridge
- 10 hosted MT5 terminals (SFCloud)
Prices in USD. Already a customer? Open SFConnect in your dashboard. All plans side by side on the pricing page.
Straight answers.
Email soporte@signalforge-ai.com if yours is not here.
Your AI, your MT5.
Create a key, connect your AI app and ask about your account. Send your first signal as a dry run and read the receipt.