Cofounder Docs
Reference
How the three surfaces name the same operation, how authentication works everywhere, and where the generated index lives.
Every operation has one canonical identifier — noun.verb or
noun.group.verb — and three spellings depending on where you call it.
Naming
| Surface | Spelling | Example |
|---|---|---|
| API operation id | noun.verb | company.email.draft.create |
| MCP tool | noun_verb | company_email_draft_create |
| CLI command | noun verb | cofounder company email draft create |
Dots become underscores on MCP and spaces on the CLI. The company.* ops
nest under cofounder company, so company.get is cofounder company get
— there's no top-level get.
A few operations also get friendlier handwritten commands that read better
than the generated spelling — company.get is cofounder company show,
and roadmap.get is plain cofounder roadmap. Both forms hit the same
operation; where they exist, the docs show the handwritten one.
A few commands don't come from operation ids at all — CLI-only harness
commands like auth and mcp setup, listed under
CLI-Only Commands.
Authentication
Authorization: Bearer <token>One header, three kinds of token: a Supabase session token
(cofounder auth token), a value in COFOUNDER_API_TOKEN, or a company API
key. MCP clients that support OAuth sign in through the browser on first
connect and need no token at all.
JSON output
CLI commands take --json; the API always answers JSON. Errors come back
status-coded, and 4xx carries the reason the request was rejected.
Command index
Command Index lists every operation family
by noun with its CLI root, MCP tool prefix, and API path. A generated
per-operation reference with full parameters is planned — for now,
cofounder <command> --help and the MCP client's tool descriptions carry
the parameter detail.