MCP server
The MCP server lets you control your account from any MCP client (Claude, or any other) over the open Model Context Protocol. It exposes the same capabilities as the dashboard — read status/positions/performance, tune every setting, flip live/dry, and place or close real orders — as MCP tools.
How it works
The server never re-implements order logic. Reads come from the tenant-scoped ledger; setting changes are
written as controls; opens/closes/flatten are queued and executed by the already-running orchestrator
with its full safety stack (buying-power guard, post-fill reconcile, no phantoms, per-engine live/dry).
Queued trades execute on the orchestrator's next cycle — typically within ~1 minute — so those tools return a
queued_command_id, not an instant fill.
Auth & isolation
- Generate a token in Settings → MCP access. It is shown once and stored only as a SHA-256 hash, scoped to exactly your tenant.
- Every call re-hashes the token and pins your tenant — you can only ever see or control your own account. There is no shared/admin token.
- Revocation is instant — regenerating or revoking blocks the next call.
Connect
Endpoint (streamable HTTP): https://sirtradesalot.com/mcp. Add this to your client's config
(replace with your token):
{
"mcpServers": {
"sirtradesalot": {
"type": "http",
"url": "https://sirtradesalot.com/mcp",
"headers": { "Authorization": "Bearer trdc_xxxxxxxx" }
}
}
}The token can also be sent as an X-Sirtradesalot-Token header if your client can't set
Authorization.
Tools — read (no side effects)
| Tool | Returns |
|---|---|
whoami() | tenant, email, name, role |
get_status() | per-engine live/dry, paper mode, trading on/off, close-only, panic, autonomous toggles, open count |
get_account() | total value, cash, buying power, day P&L (via broker) |
list_positions() | open positions (id, symbol, instrument, side, qty, entry, source, opened) |
get_performance() | win rate, wins/losses, total realized P&L |
get_settings() | gate, risk profile, sizing/caps, spread exits, wheel deltas + CSP budget, day-trade knobs |
recent_activity(limit=20) | recent events (1–200) |
list_candidates(limit=20) | recent scan candidates (1–200) |
predict(symbol) | live forecast: direction, confidence, expected move, p10/p90, last close |
Tools — control (safe; no orders placed)
| Tool | Effect |
|---|---|
pause_trading() / resume_trading() | stop / resume opening new positions (exits keep running) |
set_close_only(enabled) | close-only mode (no new opens at all) |
set_engine_enabled(engine, enabled) | toggle daytrade /
wheel_auto autonomy |
update_setting(key, value) | set any control (e.g. min_confidence,
risk_profile, wheel_put_delta, spread_take_profit, …) |
Tools — trading (act immediately)
No confirmations. This is an autonomous agent interface — these tools execute right away. The only gate is your account's mode: with paper trading ON, every action is simulated; with it OFF, the engines trade real money per their execution modes. An MCP client can flip that mode with the first two tools below, exactly like the dashboard.
| Tool | Effect |
|---|---|
set_paper_trading(enabled) | the paper-vs-live gate — simulated money on/off |
set_execution_mode(engine, mode) | flip directional/spread/wheel/daytrade to
live or dry |
open_position(symbol, instrument, side, cost, force) | queue an open (equity/option/spread); executes in the account's current mode |
close_position(position_id) | queue a close of one position |
panic_flatten() | flatten all positions + pause trading |
Safety model
- Paper vs live is the gate. There is no per-call confirmation — the account mode decides whether an action is simulated or real, and it's the same mode the dashboard shows.
- The orchestrator does the work — queued trades are sized/placed with the full safety stack (buying-power guard, post-fill reconcile, no phantoms). If the orchestrator isn't running, queued trades won't execute.
- Isolation + instant revocation — a token maps to exactly one tenant; revoking it in the dashboard blocks the next call. It will not do user management, secrets export, or touch any other tenant.
- Your token is the key. It grants full control of this one account — treat it like a password; regenerate or revoke it anytime in Settings → MCP access.