Connect an AI agent to your SystemSculpt account

Connect

Add https://systemsculpt.com/mcp to your app as a remote (Streamable HTTP) MCP server, with OAuth. The app opens the SystemSculpt sign-in page. Sign in, or sign up there if you are new, then read the consent page and choose Allow. The app keeps the token; you never copy one.

• The consent page lists every permission the app asked for. Some apps ask for all of them at once. Deny if that is more than you want.
• The token works only for your account. No tool takes another person, email or account ID.
• An app that asked for less gets insufficient_scope on a tool outside its grant. Sign in again from the app to add that permission.
• An unpaid or expired account can still connect and use every tool except sending and processing captures.

Apps we checked

Checked on November 1, 2026 on a Mac, with a test account: the app's own sign-in, then one read of that account through the app's own MCP client. "Not checked yet" means the setup follows the app's documentation, but we have not run it.

Claude Code

claude mcp add --transport http systemsculpt https://systemsculpt.com/mcp

Start claude, run /mcp, choose systemsculpt, then Authenticate. Allow in the browser. Claude Code asks for every permission at once. claude mcp remove systemsculpt removes it.

Codex

codex mcp add systemsculpt --url https://systemsculpt.com/mcp
codex mcp login systemsculpt

Codex finds the sign-in itself and opens the browser. On a machine without a browser, add --no-browser and paste the address the browser lands on. Codex asks for read access first. codex mcp logout systemsculpt disconnects.

opencode

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "systemsculpt": { "type": "remote", "url": "https://systemsculpt.com/mcp", "enabled": true }
  }
}

opencode mcp auth systemsculpt
opencode mcp list

Leave OAuth on (the default). Do not add an Authorization header.

Claude and Claude Desktop

Not checked yet. In Claude, open Settings → Connectors → Add custom connector, name it SystemSculpt, enter https://systemsculpt.com/mcp and choose Add, then Connect. Claude Desktop uses the same connectors as your Claude account. On Team and Enterprise plans an owner adds it first. See Claude's custom connector steps ↗ (opens in a new tab).

ChatGPT

Not checked yet. Where your ChatGPT plan and workspace allow custom MCP servers, add https://systemsculpt.com/mcp with OAuth. See OpenAI's plan and workspace rules ↗ (opens in a new tab).

Cursor

{
  "mcpServers": {
    "systemsculpt": { "url": "https://systemsculpt.com/mcp" }
  }
}

Not checked yet. In Cursor's MCP settings, connect SystemSculpt and allow it in the browser. The Cursor CLI uses the same file: agent mcp login systemsculpt.

VS Code

{
  "servers": {
    "systemsculpt": { "type": "http", "url": "https://systemsculpt.com/mcp" }
  }
}

Not checked yet. Run MCP: List Servers, start systemsculpt and allow it in the browser when VS Code asks.

Gemini CLI

{
  "mcpServers": {
    "systemsculpt": { "httpUrl": "https://systemsculpt.com/mcp", "oauth": { "enabled": true } }
  }
}

Not checked yet. Start Gemini CLI and run /mcp auth systemsculpt.

HTTP and your own client

Every tool is also an HTTPS endpoint under /api/account/, with the same token, input and { status, data } result. A script uses the token its OAuth client received; there is no separate key to create.

curl -s https://systemsculpt.com/api/account/plan \
  -H "Authorization: Bearer $SYSTEMSCULPT_TOKEN"

• /mcp answers 401 with WWW-Authenticate: Bearer resource_metadata="https://systemsculpt.com/.well-known/oauth-protected-resource/mcp" until a token is sent.
• That metadata names the resource https://systemsculpt.com/mcp, the authorization server https://clerk.systemsculpt.com and every scope.
• The authorization server's metadata lists its authorize, token, registration and revocation endpoints. A client identifies itself with a client ID metadata document (an HTTPS client_id) or registers dynamically.
• Use the authorization code flow with PKCE (S256) and resource=https://systemsculpt.com/mcp. A token without that resource is refused.
• Ask for offline_access to get a refresh token. Refreshing ends the previous access token.
• Send Authorization: Bearer <token> in a header, never in a URL. { "error": { "code", "message" } } is the HTTP error body.
• Keep the token in a secret store, not in a prompt, file or log.

Tools, endpoints and permissions

MCP tools/list gives each tool's input and output JSON Schema, a title and hints. Every tool that changes something is marked destructive, so your app can ask before it runs. Billing tools also list their money effects in _meta["systemsculpt.com/effects"].

• Restarting a charge (resume_subscription, resume_recurring_credits, turning on or raising set_auto_reload) needs the person to accept the exact offer from get_renewal_consent_offer. The agent shows its text word for word and passes its offerFingerprint only after the person agrees. Connecting the app is not that agreement.
• create_checkout_link returns a Stripe checkout page. Nothing is charged until the person pays there. A renewing purchase also needs the quoted terms accepted.
• create_capture, complete_capture_upload, run_capture_action and ask_captures use credits and need an idempotency key: MCP idempotency_key, HTTP Idempotency-Key header. A repeat returns the first result and charges once.
• A capture reaches your vault only when the Obsidian plugin syncs it. get_capture shows delivery.state: "verified" once the plugin confirmed the file; an agent cannot mark it delivered.
• get_license_key returns your existing plugin key, a full credential. Grant credentials:read only to an app you trust with it.
• request_account_deletion starts the same permanent deletion as the dashboard. Notes in your vault stay. After it, every other tool answers ACCOUNT_DELETION_PENDING.

Dashboard actions and their agent route