Skip to main content
Glama
Sigma-Algo

sigmavue-mcp

Official
by Sigma-Algo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
SIGMAVUE_API_URLNoThe URL of the SigmaVue API. Optional, defaults to the public SigmaVue API.https://sigmavue-api-green.onrender.com

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
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.

sigmavue_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.

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.

sigmavue_journal_listA

List trade-journal entries, newest first. Optional symbol and entry_type filters plus pagination.

sigmavue_portfolioB

Current open positions plus a rollup summary. Optional account_id and position status_filter selectors.

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.

sigmavue_copy_groups_listC

List copy-trading groups. Optional active and environment filters.

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).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.4/5.0

Scored across 8 tools

Disambiguation3/5

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.

Naming Consistency3/5

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.

Tool Count5/5

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.

Completeness3/5

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.

Resources