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

# Tylon: Git's control panel

> Tylon is where work lives and where Git happens. A column is a real branch, moving a card is a real merge. These docs cover the public API and the MCP server.

Tylon is a board whose columns are real branches. Moving a card cuts a branch, opens a pull request, or merges one — so the board cannot say "done" while the repository disagrees.

<Card title="Start here" icon="book-open" href="/concepts/cards">
  What a card is, what a column really is, and what happens when you move one. Ten minutes that make the rest of these docs read differently.
</Card>

## Reaching a board from outside

Two doors. They reach the same boards and enforce the same permissions — what differs is who is behind the call.

<Card title="Public API" icon="plug" href="/api-reference/introduction">
  A credential, a `Bearer` header, and JSON. For a deploy script, a status page, a spreadsheet — anything that has no person sitting at it.
</Card>

<Card title="MCP server" icon="terminal" href="/mcp/connect">
  For an editor or an agent working as **you**. It signs in the way you do, reads what you may read, and answers in sentences rather than in JSON.
</Card>

## Which one you want

|               | Public API                                    | MCP server                 |
| ------------- | --------------------------------------------- | -------------------------- |
| Authenticates | a machine                                     | a person                   |
| Credential    | client id and secret                          | OAuth 2.0 with PKCE        |
| Answers in    | JSON, with HTTP status codes                  | prose, for a model to read |
| Writes        | with the `write` scope and an idempotency key | yes                        |
| Set up in     | **Settings → API credentials**                | your editor, in one URL    |

If a person is present and could click **Approve**, use MCP. If nothing is present but a cron entry, use the API.
