# Seiton MCP server

MCP-compatible clients can query your analytics and manage your account through natural language. The MCP server provides the same functionality, permissions, and safety checks as the REST API and CLI.

It uses **Streamable HTTP** at `https://www.seiton.online/api/mcp`.

## Step 1 — Create an account token

Open **Settings → API / MCP** at https://www.seiton.online/dashboard/settings?tab=api

1. Pick websites: all websites, or specific ones.
2. Choose permissions (read / write per resource).
3. Name the token (for example "Cursor" or "Claude Code") and create it.
4. Copy the `sei_` secret. It is shown once.

## Step 2 — Connect your client

### Codex

```bash
codex mcp add seiton \\
  --url https://www.seiton.online/api/mcp \\
  --bearer-token-env-var SEITON_TOKEN
```

### Claude Code

```bash
claude mcp add --transport http seiton https://www.seiton.online/api/mcp \\
  --header "Authorization: Bearer sei_xxx"
```

### Cursor, Claude Desktop, and other config-based clients

```json
{
  "mcpServers": {
    "seiton": {
      "url": "https://www.seiton.online/api/mcp",
      "headers": {
        "Authorization": "Bearer sei_xxx"
      }
    }
  }
}
```

### Stdio clients (mcp-remote)

```json
{
  "mcpServers": {
    "seiton": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://www.seiton.online/api/mcp",
        "--header",
        "Authorization: Bearer sei_xxx"
      ]
    }
  }
}
```

## Tools

Resources: health, briefing, signals, analytics, revenue, churn, SEO, integrations, expenses, notifications, websites, tokens.

Naming pattern: `seiton_<resource>_<action>`

Examples: `seiton_health_overview`, `seiton_briefing_get`, `seiton_projects_list`, `seiton_integrations_sync`.

## What to ask

Paste these into Cursor, Claude Code, or Codex after the token is connected:

- Based on Seiton, what should I do this morning?
- Is revenue healthy? Any failed payments worth recovering?
- Churn is up — what's the signal, and what should I ship?

## Safety

- **Confirmation gate.** Irreversible tools (delete expense, mint or revoke a token) require `confirm: true`. Without it the tool returns a preview.
- **No secret exfiltration.** Listing tokens returns id, name, prefix, dates — never the secret.
- **Dashboard-only.** Website deletion and connecting or disconnecting payment providers stay on the web dashboard and return 403.
- **Scoped by token.** Permissions are re-validated on every tool call.

## Advanced: scoped access

Create a token limited to one website to keep an agent read-only on a single project.

Related: [API](https://www.seiton.online/api) · [CLI](https://www.seiton.online/cli) · [Tool reference](https://www.seiton.online/mcp)