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

# Overview

> Tooling for AI agents and developers — connect over MCP, point an AI coding assistant at Compass, or drive the API from the command line.

## Build Compass into your agent stack

Compass exposes a few surfaces designed for non-UI workflows:

<CardGroup cols={2}>
  <Card title="Coding Assistant" icon="robot" href="/v2/Agents/Coding-Assistant">
    LLM-optimized docs Cursor, Claude Code, Copilot, and other AI assistants can fetch directly. Drop a single URL into your project config and let the agent write the integration.
  </Card>

  <Card title="MCP Server" icon="plug" href="/v2/Agents/MCP-Server">
    A hosted Model Context Protocol server at `api.compasslabs.ai/mcp`. Connect Claude or Cursor with one URL and every Compass product becomes a native agent tool — nothing to install.
  </Card>

  <Card title="CLI" icon="terminal" href="/v2/Agents/CLI">
    A scriptable command-line interface to every Compass endpoint. Use it for one-off queries, shell pipelines, CI jobs, or as the tool layer behind an autonomous agent.
  </Card>

  <Card title="Agent Skill" icon="puzzle-piece" href="/v2/Agents/Agent-Skill">
    A packaged skill that teaches Claude Code, Cursor, or Codex to drive the CLI for you — describe a DeFi action in plain English and the agent picks the right `compass` command and runs it.
  </Card>
</CardGroup>

***

## Which one?

|                | Coding Assistant                                    | MCP Server                                                          | CLI                                                          |
| -------------- | --------------------------------------------------- | ------------------------------------------------------------------- | ------------------------------------------------------------ |
| **What it is** | Reference docs in a format AI assistants understand | A hosted server exposing every endpoint as typed agent tools        | A CLI that calls the API for you                             |
| **Used by**    | Cursor, Claude Code, Copilot, ChatGPT               | Claude Code, Claude Desktop, Cursor — any MCP client                | Humans in a terminal, shell scripts, AI agents calling tools |
| **Best for**   | Generating integration code in your project         | Letting an agent read state and build transactions directly in chat | Inspecting state, scripting workflows, agent tool use        |
| **Output**     | Generated source code in your repo                  | Typed tool results (JSON)                                           | JSON / table / TOON output to stdout                         |

Many teams use several: the coding assistant scaffolds an integration in their codebase, while the MCP server or CLI runs alongside for inspection, automation, and agent tooling.

***

## Agent-friendly by design

The CLI ships with an `--agent-mode` flag that switches output to TOON (token-efficient) format and enables structured error messages. It auto-activates when the CLI detects it's being invoked from a known agent environment (`CLAUDE_CODE`, `CURSOR_AGENT`, etc.) — so an agent calling `compass earn vaults ...` gets parseable output without you having to configure anything.

See the [CLI page](/v2/Agents/CLI) for details.

***

<CardGroup cols={2}>
  <Card title="Get Started" icon="rocket" href="/v2/get_started/get-started">
    New to Compass? Start with the SDK quickstart.
  </Card>

  <Card title="API Reference" icon="code" href="/v2/api-reference">
    Browse every endpoint the CLI and SDKs wrap.
  </Card>
</CardGroup>