Skip to main content
Chief ships first-party tools on top of the REST API and MCP server: a command-line client and a Go SDK. All of them authenticate with a Personal Access Token (pat_…) and scope to a project, the same as direct API calls.

Go SDK

Typed Go client with one service per resource. Zero third-party dependencies.

CLI

The chief command — styled output at a prompt, JSON in scripts and CI.

MCP server

Point Claude, Cursor, or Codex at your Chief project over MCP.

​
Which one to use

​
Before you start

You need a Chief account and two credentials, used by all three tools:
  1. A Personal Access Token (pat_…) — create one in the Chief app under Settings → API tokens, or follow the help center’s step-by-step.
  2. Your project id (project_…) — the project the tool reads from and writes to.
See Introduction for where to find both.

​
Install

The CLI and MCP server are distributed as single static binaries. Homebrew is the recommended install on macOS:
The Go SDK is a library — add it to a module with go get:
The go options above require a Go toolchain.

​
Shared configuration

Every tool reads the same three settings from flags, options, or the environment: See Introduction for how to create a token.

​
FAQ

Yes. The CLI, the Go SDK, and the MCP server all read CHIEF_API_KEY, CHIEF_PROJECT_ID, and CHIEF_BASE_URL, and authenticate exactly as direct API calls do.
No. The Homebrew cask installs a single static binary. A Go toolchain is only needed for the go install route or to use the Go SDK as a library.
https://api.storytell.ai. Override it with CHIEF_BASE_URL or the --base-url flag.
Call the REST API directly from any language, or drive Chief through an AI coding agent over MCP.