Model Context Protocol

Connect your agent to decisions.

Our hosted MCP server uses streamable HTTP and JSON-RPC at https://api.system1models.ai/mcp. Authenticate with Authorization: Bearer <API key>.

Tools

Four tools. One API key.

decide

Submit a model, state and exactly one typed question. Set region to global or eu. Inference uses your token allowance or prepaid balance.

Request example →

list_models

Read the live model registry, supported question types, launch prices and tiers. Text input is available; image input is coming soon.

Explore models →

get_usage

Read usage aggregates and request receipts for the account that owns your API key. Optional arguments: limit (1–100), cursor.

Usage schema →

get_balance

Read your account balance, including available, reserved and credited totals in integer nanos with the account currency.

Balance schema →

Setup

Claude Code

Set SYSTEM1_API_KEY in your local environment, then add the HTTP server.

Terminal

claude mcp add --transport http system1models https://api.system1models.ai/mcp \
  --header "Authorization: Bearer $SYSTEM1_API_KEY"

.mcp.json · Claude Code

{
  "mcpServers": {
    "system1models": {
      "type": "http",
      "url": "https://api.system1models.ai/mcp",
      "headers": {
        "Authorization": "Bearer ${SYSTEM1_API_KEY}"
      }
    }
  }
}

Claude Code configuration reference →

Cursor

Add this to ~/.cursor/mcp.json or your project’s .cursor/mcp.json. Cursor reads the key from your environment.

mcp.json · HTTP with bearer header

{
  "mcpServers": {
    "system1models": {
      "url": "https://api.system1models.ai/mcp",
      "headers": {
        "Authorization": "Bearer ${env:SYSTEM1_API_KEY}"
      }
    }
  }
}

Cursor configuration reference →

Claude Desktop

For the local claude_desktop_config.json, use the mcp-remote bridge below. It supplies the bearer header to the hosted HTTP server. Replace the key placeholder in your local config.

claude_desktop_config.json

{
  "mcpServers": {
    "system1models": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api.system1models.ai/mcp",
        "--header",
        "Authorization:${SYSTEM1_AUTH_HEADER}"
      ],
      "env": {
        "SYSTEM1_AUTH_HEADER": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}

Any stdio MCP client

Use the same JSON bridge configuration, or run the bridge from a terminal with your key in the environment.

Terminal · mcp-remote

npx -y mcp-remote https://api.system1models.ai/mcp \
  --header 'Authorization:Bearer ${SYSTEM1_API_KEY}'

mcp-remote configuration reference →

Keep your key in your local environment or private client configuration. The hosted MCP server authenticates each request; account tools return only your account’s data.