Cofounder

Reference

How one operation is named in MCP, the CLI, and the API, how to sign in on each, and where to find every command.

Each operation has one name, written three ways: for MCP, the CLI, and the API. Translate between them by swapping the separator.

Naming

SurfaceSpellingExample
API operation id
MCP tool
CLI command

The dots become underscores in MCP and spaces in the CLI. Most company.* names live under cofounder company, so company.get is cofounder company get. There's no top-level get.

Some operations also have a shorter command. company.get, for example, is also cofounder company show. Both do the same thing, and the docs show the shorter one where it exists.

A few commands, like auth and mcp setup, exist only in the CLI. They're listed under CLI-Only Commands.

Authentication

Authorization: Bearer <token>

Every request sends this header with one of three kinds of token: a sign-in session token (cofounder auth token), a value in COFOUNDER_API_TOKEN, or a company API key. MCP clients that support OAuth sign you in through the browser the first time they connect and need no token.

JSON Output

Add --json to any CLI command to get JSON. The API always returns JSON. Errors come back with a status code, and 4xx errors say why the request was rejected.

Command Index

The Command Index groups every command by what it acts on, with its CLI command, MCP tool prefix, and API path. A full per-command reference with every parameter is planned. Until then, run cofounder <command> --help or read your MCP client's tool descriptions for parameter details.