01 / Local by default
One file, per workspace.
Context lives in .memorize/MEMORY.md, directly readable and easy to carry with the project.
A workspace-local MCP server
Memory, where
the work happens.
One Markdown file. One active session. The useful context your agent needs—kept beside the project, not in another system.
Install in one prompt ↓02 / Intentional scope
Current session only.
Starting a session replaces the last one. No history, cloud sync, database, tags, index, or legacy migration layer.
03 / Bounded & searchable
64 KiB. Direct search.
Multi-word, case-insensitive section search returns the newest matches first. The cap keeps the memory useful instead of sprawling.
The entire surface area
Three tools. No detours.
A deliberately small interface for agents that need to start, remember, and resume.
| Tool | Does | Use it when |
|---|---|---|
| start_session | Creates a fresh active session, replacing the previous one. | Beginning a new work session. |
| save_memorize | Appends an update or replaces it with a compact snapshot, reporting current capacity. | Recording progress or handing work off. |
| search_memorize | Loads all context or finds the newest sections matching every query term. | Recovering the relevant part of a session. |
The agent rhythm
Start. Save. Resume.
- STEP 01
Start
Call
start_sessionwith the goal. - STEP 02
Save
Append progress; replace with a concise handoff.
- STEP 03
Search
Load all context or query just the section needed.
Setup
One prompt. Any host.
The prompt detects Codex or Claude Code, configures the matching MCP server, and leaves the other setup untouched.
SETUP PROMPT
Set up memorize-mcp for this local agent host. 1. Detect the current host. Do not configure both: - If running in Codex, use the Codex commands below. - If running in Claude Code, use the Claude Code commands below. - If the host cannot be identified, stop and ask which one to configure. 2. Confirm that git, bun, and the selected host CLI are available. If any are missing, stop and report the exact missing prerequisite. 3. Clone https://github.com/congthien2003/memorize-mcp.git into a stable user-owned tools directory outside of any application workspace. If that clone already exists, update it without deleting uncommitted user changes. 4. Change into the cloned repository and run `bun install`. 5. Run these verification commands and stop on failure: - `bunx tsc --noEmit` - `bun test src/storage/session.test.ts` 6. Configure only the selected host. First list the existing `memorize` server and remove only that server if it exists: - Codex: `codex mcp list`, then `codex mcp remove memorize` if needed. - Claude Code: `claude mcp list`, then `claude mcp remove memorize` if needed. 7. Add the server using the repository's absolute `index.ts` path: - Codex: `codex mcp add memorize -- bun "ABSOLUTE_PATH_TO_MEMORIZE_MCP/index.ts"` - Claude Code: `claude mcp add --transport stdio --scope user memorize -- bun "ABSOLUTE_PATH_TO_MEMORIZE_MCP/index.ts"` Do not set a fixed working directory, `MEMORIZE_MCP_PROJECT_ROOT`, or memory path. The server must inherit the current workspace so it writes `.memorize/MEMORY.md` in the project being worked on. 8. Run the selected host's MCP list command again and confirm that `memorize` is enabled. 9. Report the clone path, verification results, MCP list result, and the reminder to restart/reload the current host before using the new server. Do not commit or modify unrelated repositories, configurations, or MCP servers.
After setup, restart or reload the current host and use /mcp to inspect active servers.
A small boundary worth keeping