> ## Documentation Index
> Fetch the complete documentation index at: https://dev.chief.bot/llms.txt
> Use this file to discover all available pages before exploring further.

# Build on Chief

> Extend Chief with the MCP server, REST API, and CLI — bring your project's knowledge into your own agents, applications, and automations.

Chief holds everything your team has uploaded and everything it has worked out across
your chats. These tools let you reach that from outside the browser — from your AI coding
agent, your own application, your shell, and scheduled automations.

<Frame caption="The same project, two ways in: drive it from your terminal (left), or work in the Chief app (right).">
  <img src="https://mintcdn.com/chief-2d405d1a/QGBlzHNeqRlizFjv/images/demos/hero-cli-web.png?fit=max&auto=format&n=QGBlzHNeqRlizFjv&q=85&s=fc6c59a8e1c380c1ceef985f1906915a" alt="The chief CLI creating a chat in a terminal beside the same chat open in the Chief web app" width="3869" height="841" data-path="images/demos/hero-cli-web.png" />
</Frame>

You don't have to write the integration yourself. Point your favorite coding agent —
[Claude Code](https://docs.claude.com/en/docs/claude-code/overview),
[Cursor](https://cursor.com), or [Codex](https://github.com/openai/codex) — at Chief and
have it build against the API for you.

## What you can do with it

Everything you do in the Chief app, you can now do from your own stack:

* **Ask your coding agent about your project.** "What are the main themes across everything
  we've uploaded this quarter?" — answered from your Chief project, no code required. See
  [Use Chief with your AI coding agent](/ai-native).
* **Automate recurring work.** Schedule an [action](/guides/actions) that summarizes new assets
  every morning and emails your team the digest — see [what you can build](/what-you-can-build)
  for more outcomes.
* **Pull Chief into your own product.** Start a chat over your project's knowledge from your
  backend and stream the answer into your app over [REST](/api-reference/introduction).
* **Drive Chief from scripts and CI.** Bulk-upload a directory of documents, then list and
  triage them — straight from your shell with the [`chief` CLI](/tools/cli/overview).
* **Have an agent build the integration.** Hand Claude Code your API token and this
  reference, and ask it to write the script that does the job. It reads the docs and builds
  it.

## Three ways to build

The MCP server and the REST API are two peers for building on Chief — connect an agent over
MCP, or call the API directly from any language. The CLI is the tool for the shell and CI.

<CardGroup cols={3}>
  <Card title="MCP server" icon="robot" href="/mcp/overview">
    Give Claude Code, Cursor, or Codex direct access to your project. No SDK, no curl.
  </Card>

  <Card title="REST API" icon="code" href="/api-reference/introduction">
    Build directly against the API from any language. Every endpoint, with an interactive
    playground.
  </Card>

  <Card title="CLI" icon="terminal" href="/tools/cli/overview">
    The `chief` command for your shell, scripts, and CI — styled output or JSON.
  </Card>
</CardGroup>

Prefer Go? The [Go SDK](/tools/go-sdk) is a typed client with one service per resource, and
it's what the CLI and MCP server are built on.

## Get started

<CardGroup cols={2}>
  <Card title="What you can build" icon="lightbulb" href="/what-you-can-build">
    Five concrete outcomes you can ship on Chief — and the shortest path to each.
  </Card>

  <Card title="Use Chief with your AI coding agent" icon="sparkles" href="/ai-native">
    New here? Connect your agent and ask your first question in minutes — no curl required.
  </Card>

  <Card title="Quickstart" icon="rocket" href="/quickstart">
    Zero to a chat response with plain `curl`.
  </Card>

  <Card title="Tools overview" icon="screwdriver-wrench" href="/tools">
    The Go SDK, the `chief` CLI, and the MCP server, side by side.
  </Card>

  <Card title="API reference" icon="book-open" href="/api-reference/introduction">
    Authentication, errors, pagination, and every endpoint.
  </Card>
</CardGroup>