memory_exploration_record

Saves the conclusion of a codebase exploration together with the SHA-256 of every file read to reach it, so a later session can reuse it while those files are unchanged.

local stdio server writes idempotent

Caution. Files outside root are refused. Up to 64 files of at most 32 MB each.

When to use

You answered a structural question ("how is auth wired?", "where is the retry policy decided?") by reading several files.
You expect the same question again in a later session and want to skip re-reading the files.
An earlier memo for the same question is out of date: recording it again for the project replaces it.

Parameters

Name	Type	Default	Description
`question`required	string	—	The question the exploration answered, e.g. 'how is auth wired?' (min length 1, max length 2,000)
`conclusion`required	string	—	What was concluded, self-contained enough to reuse without re-reading (min length 1, max length 20,000)
`files`required	string[]	—	Files read to reach the conclusion: paths relative to root, or absolute paths inside root
`project`required	string	—	Project name (min length 1, max length 200)
`root`	string	—	Absolute project root directory; default: the server's working directory (max length 1,024)

Example

Arguments

{
  "question": "how is auth wired?",
  "conclusion": "JWT validation runs in middleware/auth.py before every /api route; tokens are issued in services/tokens.py and refresh tokens live in the refresh_tokens table.",
  "files": [
    "middleware/auth.py",
    "services/tokens.py"
  ],
  "project": "my-api",
  "root": "/Users/dev/projects/my-api"
}

Result shape

{
  "recorded": true,
  "id": 12,
  "project": "my-api",
  "root": "/Users/dev/projects/my-api",
  "replaced": false,
  "semantic_index": true,
  "files": [
    {
      "path": "middleware/auth.py",
      "sha256": "3f9a1c…e04b",
      "size": 4812
    },
    {
      "path": "services/tokens.py",
      "sha256": "81d27e…a9c3",
      "size": 2290
    }
  ]
}

Paths are stored relative to root. semantic_index is false when the embedding model was unavailable; the memo is then found by word overlap only.

Values are illustrative; the keys follow the server's handler. MCP clients receive the result as JSON text content.

Server description

The description the server sends to your agent in tools/list, captured from the v14.9.0 source:

Record the conclusion of a codebase exploration together with the SHA-256 of every file read to reach it. Call it after answering a structural question by reading files (how X is wired, where Y is decided). Paths are stored relative to `root` (default: the server's working directory); files outside root are refused. Up to 64 files of at most 32 MB each. Recording the same question again for the project replaces the earlier memo.

When to use

Parameters

Example

Server description

Related tools