CLI and MCP setup

Install the published @superember/cli package and run superember auth login --client-id …. The CLI uses OAuth Authorization Code with S256 PKCE and a loopback callback; CI can set SUPEREMBER_TOKEN to a scoped service-account token. Add --json for automation, --wait for terminal operation status, and --file - to read JSON or YAML from stdin.

superember team create --file team.yaml --wait --json
superember agent create --team revenue --parent Rowan --file agent.yaml --wait --json
superember fleet plan --file fleet.yaml --wait --json
superember activity list --limit 20 --json
superember pulse get --json
superember agent conversation list Scout --json

Configure MCP clients with URL https://api.superember.ai/mcp. OAuth-capable clients discover authorization metadata automatically. For headless clients, set an Authorization: Bearer … header using a narrowly scoped service account. Tools are task-oriented (team_create, agent_create, agent_configure, activity_list, agent_approval_respond, delegation_delivery_recover, fleet_plan, fleet_apply, workflow_*) and resources use superember://… URIs. Provider authorization is returned as an interactive handoff rather than asking the model for secrets.

Start here

Onboarding

Workforce and delegation

Workflows and approvals

Knowledge, tools, and files

Core concepts

Developers

Reference

Trust and troubleshooting