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

# Introduction

> Your Doers workspace, reachable from scripts over REST and from AI assistants over MCP.

Doers exposes your workspace in three ways, all derived from **one list of operations**. An operation is
declared once, and the REST route, the MCP tool and the CLI command are generated from that single
declaration: same input, same output, same errors.

<CardGroup cols={2}>
  <Card title="REST API" icon="code" href="/quickstart">
    193 operations under `https://api.doers.sh/v2`, described by an OpenAPI 3.1 document. For
    scripts, n8n, cron jobs and backends.
  </Card>

  <Card title="MCP server" icon="plug" href="/mcp/introduction">
    186 of those operations as Model Context Protocol tools, plus resources and prompts. For Claude,
    ChatGPT, Cursor, VS Code and any other MCP client.
  </Card>
</CardGroup>

The `doers` command-line client is generated from the same list (`doers tasks list`,
`doers plan suggest`). It is not published to a package registry yet; every tool page still shows
its CLI command.

## Addresses

| What             | Where                                                 |
| ---------------- | ----------------------------------------------------- |
| REST API         | `https://api.doers.sh/v2`                             |
| OpenAPI document | `https://api.doers.sh/openapi.json` (no token needed) |
| MCP server       | see [Connecting a client](/mcp/connecting)            |

## What you can reach

| Domain                    | What it covers                                                                                                         | MCP reference                                                                                           |
| ------------------------- | ---------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------- |
| Tasks                     | list, read, create (fields or a sentence), update one or many, schedule, tick, archive, delete, checklists, assignment | [Tasks](/mcp/reference/tasks)                                                                           |
| Projects, areas, headings | the structure tasks live in                                                                                            | [Projects](/mcp/reference/projects), [Areas](/mcp/reference/areas), [Headings](/mcp/reference/headings) |
| Context and search        | the scored priorities, cross-entity search, identity, statistics, activity                                             | [Context and search](/mcp/reference/context)                                                            |
| Planning                  | the day's plan, ADHD-mode rounds, work sessions, the journal, habits                                                   | [Planning](/mcp/reference/planning)                                                                     |
| Comments and files        | comments and file links on tasks, projects and areas                                                                   | [Comments and files](/mcp/reference/comments-and-files)                                                 |
| Calendar                  | the connected Google Calendar's calendars and events                                                                   | [Calendar](/mcp/reference/calendar)                                                                     |
| Coach                     | the AI coach's threads, status and settings                                                                            | [Coach](/mcp/reference/coach)                                                                           |
| Sharing and workspaces    | people on a task, project or area, share links, team workspaces                                                        | [Sharing](/mcp/reference/sharing), [Workspaces](/mcp/reference/workspaces)                              |
| Agents                    | agent packages, installs, the marketplace, paired devices                                                              | [Agents and packages](/mcp/reference/agents)                                                            |
| Account                   | profile, API tokens, connected applications, referrals, team seats                                                     | [Account](/mcp/reference/account)                                                                       |

Notes and local agents live in a folder on your own computer, read by the desktop app. The server
holds no copy of them, so neither the API nor the MCP server can read them.

## Conventions

* **JSON** in and out, UTF-8.
* **Days** are `YYYY-MM-DD`, **times** are `HH:MM` (24 h), **timestamps** such as `completedAt` are
  milliseconds since the epoch, **identifiers** are UUIDs.
* **Lists are bounded.** When a response carries `nextCursor`, call again with `cursor` set to it
  until it comes back `null`. The cursor is opaque.
* **Errors** share one envelope, `{ "error": { "code", "message", "details"? } }`, with a stable
  machine code and an English message. See [Errors](/errors).
* **Your day, not the server's.** The server works in UTC. Send `X-Doers-Today: YYYY-MM-DD`, or the
  `day` argument where an operation takes one, so "today" means your today.

## Two things to know first

<Note>
  **`when` is not `deadline`.** `when` is when you plan to do the task (`today`, `anytime`,
  `someday` or a date). `deadline` is when it is due. They are independent fields, and confusing
  them is the most common mistake. See [Data model](/concepts/data-model).
</Note>

<Note>
  **Archive first.** Archiving a task, project or area is reversible (`restore: true`). Deleting one
  for good is refused until it has been archived.
</Note>

<Card title="Make your first call" icon="bolt" href="/quickstart">
  Create a token, read your context, and add a task from a sentence.
</Card>