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

# MCP

> Connect an AI client to Superthread and work with notes and saved note templates.

The [Superthread MCP server](https://mcp.superthread.com/mcp) connects an AI client to your workspace. Add `https://mcp.superthread.com/mcp` as a remote MCP server in your client's connection settings and follow its sign-in flow. Operations use the authenticated caller's Superthread permissions.

For built-in and custom Superthread agents, see [agents](/docs/help/agents). For terminal access, see the [CLI reference](/docs/cli/index).

## Notes and templates

Ask your AI client to read the note and its current enhanced version before editing it. Notes use exact saved note IDs, and templates use exact IDs returned by the template list. Titles and URLs are not substitutes for these IDs.

### Note template operations

* `note_template_list` lists all templates accessible to the caller, including their IDs, context, and ordered sections.
* `note_template_get` reads a saved template by `template_id`.
* `note_template_update` edits an owned template by `template_id`, with an `update` object containing `title`, `context`, or `sections`.

Omitted fields stay unchanged. `context: ""` clears the template instructions. `sections: []` clears sections; any other sections array replaces the whole ordered list. Each section has `title` and `description` fields. Read the template before replacing its sections so you preserve sections you still need.

Only the owner can update a template. Shared and built-in templates may be readable without being editable. These tools edit existing templates; creating and deleting templates are not included. See [note templates](/docs/help/note-templates) and the [template API references](/docs/api-docs/notes/get-note-templates).

### Note enhancement operations

* `note_get` reads the saved note, its `revision`, its enhanced entries in `ai_notes`, and its current `last_note_template_id`.
* `note_enhance` starts a revision or re-enhancement using `note_id` and an `enhancement` object.
* `note_enhancement_get` reads the latest operation for `note_id`, or a specific operation when you supply `operation_id`.

In `enhancement`, provide non-empty `instructions`, an explicit `note_template_id`, or both. Instructions alone revise the existing saved enhanced HTML. Optional `enhanced_note_id` chooses a saved enhanced entry; otherwise the entry matching `last_note_template_id` is used. An explicit template regenerates from raw user notes and the transcript, and can include extra instructions. Neither mode changes the original notes, transcript, or saved template.

Supply the `expected_revision` from `note_get` to protect concurrent edits. An optional UUID `operation_id` identifies an identical retry. If omitted, the adapter supplies the current revision and an operation UUID. Reusing an operation ID with different input, starting a second operation while one runs, or using a stale revision fails with a conflict.

Operations have `idle`, `running`, `completed`, or `failed` status. A running operation's `content` is an unsaved preview. Only `completed` with `ai_note` confirms the enhanced result has been saved. If generation is still running, use `note_enhancement_get` with its operation ID. A failed operation is reported as an error: read the note again before retrying a conflict, and do not treat preview content as a saved result.

Only the note owner can start or observe an enhancement. A custom agent's note read grant permits `note_get`, but does not grant either enhancement operation. See [enhance or revise a note](/docs/api-docs/notes/enhance-a-note), [observe enhancement progress](/docs/api-docs/notes/get-note-enhancement), and the [CLI equivalents](/docs/cli/notes#enhance-or-revise-a-note).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.