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

# MCP reference

> The local Termyte tools available to MCP clients.

# MCP tools

Termyte's MCP server uses newline-delimited JSON-RPC over stdin and stdout. It advertises protocol version `2024-11-05`.

Search limits must be integers from 1 to 100. Context token budgets must be integers from 256 to 200,000. The default context budget is 4,000 tokens.

## Search and context

| Tool                      | Required input | Purpose                                                                           |
| ------------------------- | -------------- | --------------------------------------------------------------------------------- |
| `termyte.search`          | `query`        | Search traces, observations, memories, summaries, episodes, or all document types |
| `termyte.context`         | `query`        | Build an attributable, token-budgeted context packet                              |
| `termyte.get_trace`       | numeric `id`   | Fetch one trace                                                                   |
| `termyte.get_observation` | numeric `id`   | Fetch one observation                                                             |
| `termyte.get_memory`      | numeric `id`   | Fetch one memory                                                                  |
| `termyte.explain`         | string `id`    | Show provenance, lifecycle, feedback, and measured effects                        |

Search and context accept optional repository, session, file, type, and limit filters. `termyte.context` also accepts `tokenBudget`.

## Feedback and health

| Tool               | Required input                      | Purpose                                      |
| ------------------ | ----------------------------------- | -------------------------------------------- |
| `termyte.feedback` | `id`, `event`, `contextInjectionId` | Record feedback for a delivered memory       |
| `termyte.health`   | none                                | Report database, queue, and retrieval health |
| `termyte.stats`    | none                                | Report local storage and retrieval counts    |

Feedback events are `shown`, `used`, `helpful`, `harmful`, `ignored`, `downranked`, and `corrected`. A correction also requires `correctionText`.

## Work Thread continuity

| Tool                  | Required input                                   | Purpose                                               |
| --------------------- | ------------------------------------------------ | ----------------------------------------------------- |
| `termyte.task_create` | `repo_id`, `title`, `objective`                  | Create a Work Thread task                             |
| `termyte.task_get`    | `taskId`                                         | Read current Work Thread state                        |
| `termyte.step_add`    | `taskId`, `title`, `position`, `expectedVersion` | Add a step with stale-write protection                |
| `termyte.resume`      | `taskId`                                         | Build a resume packet; `workspaceRoot` adds Git drift |
| `termyte.handoff`     | `taskId`, `source`, `target`                     | Store a cross-agent handoff packet                    |

Handoff source and target values are `claude-code`, `codex`, and `opencode`.

## Compatibility aliases

The server still registers `search_memories`, `get_memory`, `get_recent_sessions`, `get_session`, and `get_observations_for_session` for older clients. New integrations should use the `termyte.*` names.