Positive Skew MCP

Native MCP tools for driving a Positive Skew account from Claude Desktop, Claude Code, Cursor, Codex, or any other MCP-aware client.

Safety Harness

The MCP server intentionally exposes no manual order-placement tool in paper or live modes. Use your broker or another execution surface for discretionary orders. Agents can inspect existing orders and cancel an order as a risk-reduction control; systematic executions continue to originate from the trading pipeline.

The server runs locally over stdio and reuses the same session file as the headless CLI:

~/.config/pskew/config.json

Quick Start

# Install both the CLI and the MCP binary
npm install -g @positive-skew/cli @positive-skew/mcp

# Sign in once
pskew signin --email [email protected]

# Register pskew-mcp with every detected MCP client
pskew mcp install

Then restart your MCP client and the positive-skew tools will be available.

Manual Registration

If you prefer to wire things up by hand:

Claude Code

claude mcp add -s user positive-skew -- pskew-mcp

Claude Desktop

Add this to claude_desktop_config.json using an absolute path. Claude Desktop does not always inherit your shell PATH.

{
  "mcpServers": {
    "positive-skew": {
      "command": "/usr/local/bin/pskew-mcp"
    }
  }
}

Find the absolute path with which pskew-mcp.

Cursor

Add this to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "positive-skew": {
      "command": "/usr/local/bin/pskew-mcp"
    }
  }
}

Codex

Add this to ~/.codex/config.toml:

[mcp_servers.positive-skew]
command = "/usr/local/bin/pskew-mcp"

Multiple Profiles

Register one entry per profile with a PSKEW_PROFILE env override:

{
  "mcpServers": {
    "positive-skew-personal": {
      "command": "/usr/local/bin/pskew-mcp",
      "env": { "PSKEW_PROFILE": "default" }
    },
    "positive-skew-entity": {
      "command": "/usr/local/bin/pskew-mcp",
      "env": { "PSKEW_PROFILE": "entity" }
    }
  }
}

Environment

The server uses the same Supabase configuration as the CLI. Positive Skew production is the default; these environment variables are optional explicit overrides:

• PSKEW_SUPABASE_URL and PSKEW_SUPABASE_ANON_KEY
• PSKEW_SUPABASE_ENV=staging
• PSKEW_SUPABASE_URL_STAGING and PSKEW_SUPABASE_ANON_KEY_STAGING
• PSKEW_PROFILE to select a profile
• PSKEW_SESSION_PATH to override the session file
• PSKEW_TELEMETRY=0 to disable optional telemetry headers

The MCP server does not load .env files from its current working directory. Pass overrides through the MCP client's env configuration.

Safety Model

Read tools are unrestricted. Write tools default to dry-run mode and return a structured diff. Call the same tool again with confirm: true to apply the change.

Every tool requires a rationale argument: a short explanation of the user intent behind the call. Do not include secrets, credentials, tokens, or private chat transcripts. Tools also expose optional context seeds such as analysis_focus, change_reason, trigger_reason, cancel_reason, and forecast_basis when that context helps Positive Skew understand the workflow.

Switching into live-alpaca requires both confirm: true and allow_live: true.

The server also exposes JSON resources for the current strategy, today's Skew, latest forecasts, and latest digest, plus positive-skew://docs/agent-guide for agent-specific operating instructions.

Feedback

Agents can call report_agent_feedback when a workflow is blocked, confusing, or repeatedly requires awkward multi-tool stitching. The tool records what the agent was trying to do, which tools it tried, what happened, and what it expected so the MCP surface can improve over time.