Your MT5, now with an API.
SFConnect is the SignalForge API and MCP server for MetaTrader. Submit signals from your own code, read an acknowledgment for every execution, and let AI agents operate through the same scoped keys - with dry-run as the default so nothing moves until you say so.
What SFConnect is, in sixty words.
SFConnect is the public API and MCP server of SignalForge. You create keys in the dashboard (read, or read plus trade), submit signals to MT4/MT5 from your own code or scripts, and get an acknowledgment with a signal id for every execution or rejection. AI agents connect through the same MCP server. Included from the Trader plan at $14.99/mo. Updated October 31, 2026.
Three doors into your account.
One key, three ways to use it - code, scripts or an AI agent that does the typing.
Execute from your code
Submit buy, sell and close signals with SL/TP, lot or risk sizing, and per-account routing - the same execution engine the webhook bridge uses, without TradingView in the middle. Anything that can send an HTTPS request works: Python, Node, a cron job, a spreadsheet add-on.
Verify everything
Every submission returns a receipt: signal id, decision, and the exact rejection reason when a filter or a market condition says no. Poll status, read recent signals, build your own journal. No execution is a black box.
Let AI agents operate
The same capabilities are exposed as an MCP server, the standard protocol AI clients speak. Claude, Cursor or your own agent can check recent signals, submit a trade and read the acknowledgment - with the same scopes and the same dry-run default as a key. Human in the loop stays optional, not accidental.
One payload, one POST.
Bearer key in the header, JSON in the body, receipt in the response. Full reference is public.
The shape of a signal
{"symbol":"EURUSD","action":"buy","lot":0.01,"sl":50,"tp":100,"dry_run":true}Dry-run is the default: the same validation, sizing and filters as a live signal, zero orders. Create a key in the dashboard (read, or read plus trade), revoke it in one click, and route to a specific account on multi-account plans. Full reference, auth and examples →
Power with guardrails.
An API that can trade needs brakes designed in, not bolted on.
Scoped keys
A key can read, or read and trade - nothing else. Compromise of a read key cannot move money. Revocation is instant from the dashboard.
Dry-run by default
Every client - your script or an AI agent - starts in dry-run. The full path runs, the receipt comes back, no order is placed. Going live is an explicit scope, not a default.
No account password shared
Execution flows through your SignalForge setup into your own MetaTrader terminal - the same model as the webhook bridge. Your broker credentials are never part of any API call.
Before you ask.
Which plans include SFConnect?
Trader, Pro and Elite. Starter keeps the webhook bridge, SFCopier and everything else - the API and MCP server arrive with the Trader plan at $14.99/mo.
Does it work with MT4 and MT5?
Yes. Both platforms, the same payload, the same receipts - including prop-firm accounts with symbol suffixes and custom names.
What is MCP, exactly?
Model Context Protocol - the open standard that lets AI applications call external tools safely. If your AI client supports MCP servers, it can operate SFConnect without any custom integration. The MCP guide explains it in depth →
Can an AI agent place live trades?
Only with a key that has the trade scope, and even then dry-run is the default mode. Every action lands in your activity with its receipt, so an agent is as auditable as a human trader.
Where are the docs?
Public, no login: api.signalforge-ai.com/docs/api. The TradingView API guide covers the webhook path, and the AI trading agents guide the agentic one.
Your code, your MT5.
Create a key, send a dry-run signal, read the receipt.