sigmavue-mcp
OfficialClick on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@sigmavue-mcp show my current portfolio"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
SigmaVue CLI
Control your SigmaVue trading account from the terminal —
and from any MCP-speaking assistant. sigmavue is a thin, read-mostly client
over the public SigmaVue API: check status, journal, and portfolio; manage broker
accounts and copy-trading groups; and place kill-switch-gated simulated trades —
without clicking through the app.
It adds no backend logic and bundles no trading strategies. Every command maps to an API endpoint that already ships. Trade execution is fail-closed and SIM-only.
Install
Run it without installing (requires uv):
uvx --from git+https://github.com/Sigma-Algo/sigmavue-cli sigmavue --helpInstall from source:
git clone https://github.com/Sigma-Algo/sigmavue-cli
cd sigmavue-cli
uv sync # or: pip install -e .
uv run sigmavue --help
pip install sigmavue— coming soon (PyPI publish pending).
Related MCP server: IBKR MCP Server
Quickstart
# Point at the API (optional). Defaults to the public SigmaVue API.
export SIGMAVUE_API_URL=https://sigmavue-api-green.onrender.com
# or http://localhost:8000 for a local backend.
sigmavue login --email you@example.com # password read at a secure prompt
sigmavue status # health + account summary
sigmavue accounts list # broker accounts your token owns
sigmavue journal list --symbol NQ # trade journal
sigmavue portfolio # open positions + rollup
sigmavue trade execute --symbol NQ --qty 1 --side buy --sim # SIM-only
sigmavue copy groups list # copy-trading groupsThe bearer token is stored at ~/.sigmavue/auth.json (file mode 0600).
Passwords are only ever read from a prompt, never accepted as an argument.
Commands
Command | What it does |
| Authenticate; store or clear the local token |
| Backend health + current user + account summary |
| List broker accounts your token is scoped to ( |
| Start a broker OAuth connect (returns an |
| Remove a broker account by id |
| List managed trading profiles (enterprise) |
| List trade-journal entries ( |
| Current positions + summary ( |
| Place an order — kill-switch gated, |
| List copy-trading groups |
| Create a copy-trading group |
| Coming soon — use the app for now (see below) |
Exit codes: 0 success · 1 validation / API / trade-refused · 2 not logged in.
Trading safety
Trade execution is fail-closed and re-checked on every call, before any order request leaves your machine:
CLI live-execution is disabled —
--simis required; SIM routes to your active demo broker account.Local kill-switch — the CLI refuses to place an order whenever trading is turned off, via any of:
env
TRADING_ENABLEDset to0/false/no/off~/.sigmavue/killswitch.jsonwith{"paused": true}(a missing or corrupt file also blocks — fail-closed)~/.sigmavue/TRADING_ENABLEDfile containing0
Paths are overridable via
SIGMAVUE_KILLSWITCH_PATHandSIGMAVUE_TRADING_ENABLED_PATH.Backend circuit breaker — the order is refused unless the server-side per-user circuit breaker is
CLOSED.
Rate limits are respected: a stable User-Agent/X-SigmaVue-Client is sent, and
429 responses trigger bounded Retry-After backoff (--verbose surfaces the
rate-limit headers).
MCP server
The same capability layer is exposed as an MCP
server, so phone / agent coding assistants get identical reach over one API. It
speaks stdio and reads the SAME token sigmavue login stores — there is no
credential collection in the MCP surface.
uv sync --extra mcp # or: pip install "sigmavue[mcp]"
sigmavue login # once, in a terminal
uv run sigmavue-mcp # serves over stdioAdd it to an MCP client (use an absolute path so it can start from anywhere):
{
"mcpServers": {
"sigmavue": {
"command": "uv",
"args": [
"--directory", "/ABSOLUTE/PATH/TO/sigmavue-cli",
"run", "sigmavue-mcp"
]
}
}
}Claude Code:
claude mcp add sigmavue -- \
uv --directory /ABSOLUTE/PATH/TO/sigmavue-cli run sigmavue-mcpIt exposes eight tools: sigmavue_status, sigmavue_accounts_list,
sigmavue_clients_list, sigmavue_journal_list, sigmavue_portfolio,
sigmavue_trade_execute, sigmavue_copy_groups_list, and
sigmavue_copy_groups_create. Interactive/destructive flows (login, broker
connect/remove) stay CLI-only.
Enterprise
Command breadth is decided server-side by your token: a member sees their own
accounts, a manager/enterprise token sees everything it owns — the same
accounts list command covers both. A dedicated multi-tenant clients endpoint is
on the roadmap; clients list maps to managed trading profiles today.
Adding copy-trade followers (coming soon)
copy groups add-follower is intentionally not enabled from the CLI or MCP yet:
there is no atomic add-follower endpoint, and a client-side read-modify-write of
the follower list would be unsafe. A server-side
POST /api/v2/trading-groups/{id}/followers is planned; until then, add
followers in the SigmaVue app. copy groups list and create work fully.
Development
uv sync
uv run pytest -q # tests use httpx.MockTransport — no live API callsLicense
Available Tools
8 toolssigmavue_accounts_listA
List every broker account the caller's token is scoped to. Breadth is
decided server-side by the token (a member sees their own; a manager token
sees all it owns). Optional is_active filter and pagination.
Inputs: page, is_active, page_size. Returns: object
sigmavue_clients_listA
List managed trading profiles (maps to /users/trading-profiles). A
dedicated enterprise "clients" endpoint is a documented backend gap; for full
breadth today use sigmavue_accounts_list.
Inputs: no named parameters. Returns: object
sigmavue_copy_groups_createA
Create a copy-trading group with a leader account and optional followers. Adding followers to an EXISTING group is intentionally not exposed over MCP (honest-disabled in the capability layer — needs an atomic server endpoint).
Inputs: name (required), ticker (required), leader_account_id (required), environment, +1 more. Returns: object
sigmavue_copy_groups_listC
List copy-trading groups. Optional active and environment filters.
Inputs: active, environment. Returns: object
sigmavue_journal_listA
List trade-journal entries, newest first. Optional symbol and
entry_type filters plus pagination.
Inputs: page, symbol, page_size, entry_type. Returns: object
sigmavue_portfolioB
Current open positions plus a rollup summary. Optional account_id and
position status_filter selectors.
Inputs: account_id, status_filter. Returns: object
sigmavue_statusA
Backend health plus, when a token is stored, the current user and account
summary. Safe to call unauthenticated — it reports authenticated: false
with a login hint rather than erroring.
Inputs: no named parameters. Returns: object
sigmavue_trade_executeA
Place an order — fail-closed. Mirrors the CLI exactly: live execution is
disabled (pass sim=true to route to the active demo account), and the
operator kill-switch + backend circuit breaker are re-checked on every call
BEFORE any network write. When the kill-switch is engaged the tool refuses
with blocked: true and places nothing.
Inputs: side (required), symbol (required), quantity (required), sim, +2 more. Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 8 tools
Most tools have distinct purposes, but 'sigmavue_accounts_list' and 'sigmavue_clients_list' overlap significantly; the description of clients_list explicitly directs users to accounts_list for full breadth, causing potential confusion for an agent.
Tools consistently use the 'sigmavue_' prefix and generally follow a verb_noun pattern (e.g., 'accounts_list', 'trade_execute'), but 'portfolio' and 'status' are nouns only, and 'trade_execute' inverts the typical verb_noun order, creating minor inconsistency.
With 8 tools covering accounts, clients, copy groups, journal, portfolio, status, and trade execution, the count is well-scoped for a trading platform MCP server—neither too few nor excessive.
The tool surface covers essential listing and execution operations, but notable gaps exist: no way to update or delete copy groups, no close-position tool, and no order-specific detail retrieval beyond journal entries.
Related MCP Connectors
Trading MCP server for AI agents, with live market data, account reads and controlled execution.
Hosted MCP server for MT4 and MT5: read accounts, prices and candles, and place or close orders.
MCP server for OpenMM — exposes market data, account, trading, and strategy tools to AI agents
MCP server for Gainium — manage trading bots, deals, and balances via AI assistants
Related MCP Servers
- FlicenseCqualityDmaintenanceAn MCP server that provides an interface for the Interactive Brokers API via the ib_async library. It enables users to manage accounts, access real-time and historical market data, and execute or monitor trades through TWS or IB Gateway.331-
- AlicenseNot gradedqualityDmaintenanceAn MCP server for Interactive Brokers, enabling account management, trading operations, and market data queries.8MIT
- FlicenseNot gradedqualityDmaintenanceUniversal MCP server that enables AI assistants to control MetaTrader 5 directly, executing trades, managing data, and automating MT5 operations through natural language.4-
- AlicenseCqualityBmaintenanceLocal paper-trading and market simulation MCP server for multi-account portfolios, advanced orders, options/futures, backtesting, alerts, and automation.60MIT