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
| You want to… | Use |
|---|---|
| Build a Go service or automation | Go SDK |
| Script Chief, run it in CI, or drive it from a shell | CLI |
| Give a coding agent access to your project | MCP server |
| Call from another language | The REST API directly |
Before you start
You need a Chief account and two credentials, used by all three tools:- A Personal Access Token (
pat_…) — create one in the Chief app under Settings → API tokens. - Your project id (
project_…) — the project the tool reads from and writes to.
Install
The CLI and MCP server are distributed as single static binaries. Homebrew is the recommended install on macOS:go get:
go options above require a Go toolchain.
Feature availability
The tools expose every Chief resource, but the public API backs some of them today and the rest are rolling out.Available now: chats, assets, and labels.Rolling out: actions, skills, memories, live sessions, and projects.
These require the latest Chief API release. Commands and methods for them are
documented but may return errors until the rollout completes.
Shared configuration
Every tool reads the same three settings from flags, options, or the environment:| Setting | Environment variable | Notes |
|---|---|---|
| API key | CHIEF_API_KEY | Personal Access Token (pat_…), sent as X-API-Key. Required. |
| Project | CHIEF_PROJECT_ID | Sent as X-Project-Id. Required for project-scoped resources. |
| Base URL | CHIEF_BASE_URL | Defaults to https://api.storytell.ai. |