[ HEADLESS · API-FIRST ]
Headless, because the user who never logs in wins.
BossMode ships three first-class surfaces together: a CLI, an MCP server, and a REST API. The architecture Salesforce announced at TDX 2026 — shipped months earlier, with your existing vendor CLI keeping its own OAuth.
[ THREE SURFACES · ONE CONTROL PLANE ]
Every way a machine can reach BossMode.
$_
@bossmode/cli
npm-installed. Runs on your laptop, a CI runner, or a remote box. Spawns your existing Claude / Codex / Hermes / OpenClaw under its own OAuth — we never hold vendor tokens.
CLI docs → →⬡
@bossmode/mcp-server
Stdio MCP server. Drop into Claude Desktop, Claude Code, Continue, Cursor, Zed — 27+ tools for directives, approvals, reports, packs, devices, AvatarCzar. No adapter glue.
MCP docs → →{}
/api/pro/*
Plain HTTP + x-bossmode-token. OpenAPI-described. Rate-limited per workspace, not per seat. Works with whatever HTTP client your pipeline already has.
API docs → →[ HOW WE STACK ]
The Salesforce-at-TDX playbook, shipped.
Salesforce announced Headless 360 on 2026-04-15. BossMode shipped with that architecture from day zero. Sources: Salesforce TDX keynote (2026-04-15), ServiceNow Now Assist public docs.
| Feature | BossMode | Agentforce | Now Assist |
|---|---|---|---|
| Local-first execution | Yes — daemon runs on your machine | No (cloud-only) | No (cloud-only) |
| CLI surface | Yes (@bossmode/cli, npm) | Yes (sf CLI) | Limited |
| MCP tool server | Yes — 27+ tools, stdio | Announced at TDX 2026 | Not announced |
| REST API | Yes — OpenAPI | Yes | Yes |
| Harness-agnostic (Claude / Codex / Hermes / OpenClaw) | Yes — vendor OAuth stays with you | Agentforce only | Now Assist only |
| Operator approval gates | Yes — every destructive op is gated | Partial | Admin-only flows |
| Revenue tracking built in | Yes — per-action result audit | Via CRM integration | Via ITSM workflows |
| Architecture shipped | Headless-first from day zero (2026-03) | Retrofitting — announced 2026-04-15 | UI-first |
| Pricing | Per-workspace flat tiers | Per-action consumption (announced at TDX) | Per-seat enterprise licensing |
[ THREE WAYS TO GIVE AN ORDER ]
Same directive. Three ways in.
# Pair this device with your workspace + start the daemon.
npx @bossmode/cli@latest init --wizard
# Give a directive from anywhere.
bossmode directive "draft the weekly brief for Tuesday"Runs on your laptop, a CI runner, or a remote SSH session.
{
"mcpServers": {
"bossmode": {
"command": "npx",
"args": ["-y", "@bossmode/mcp-server"],
"env": {
"BOSSMODE_API_TOKEN": "cp_live_..."
}
}
}
}Paste into ~/Library/Application Support/Claude/claude_desktop_config.json. The server exposes 27+ BossMode tools.
# Pull the full consigliere context (signals, packets, orders, metrics).
curl -X GET https://bossmode.ing/api/pro/context \
-H "x-bossmode-token: cp_live_..."Plain HTTP. Wire BossMode into any pipeline that speaks JSON.
[ WHO THIS IS FOR ]
Built for teams who operate headless by default.
AI-native engineering teams
Your platform thesis already assumes agents talk to services, not humans clicking UIs. BossMode fits that architecture without adapter glue.
Agencies wiring clients’ agents together
One MCP server, many client workspaces, clean audit trail per tenant. Charge for BossMode seats while keeping the tooling consistent.
Platform engineers running multi-tenant AI ops
Role-scoped tokens, consumption telemetry, signed webhooks, per-tenant isolation — all shipped. No "enterprise edition" paywall.
[ WIRE IT IN ]
Three surfaces. One control plane. Your stack in the next hour.
Sign up, install the CLI, point your MCP host at @bossmode/mcp-server, or hit the REST API directly — whichever fits your stack. Same control plane either way.