Structured session journals for AI agents. Persistent memory across sessions.
Structured session journals for AI agents. Persistent memory across sessions -- no more repeating dead ends.
When a session ends, all reasoning is lost -- what was tried, what failed, what's blocked. The next session starts from scratch and repeats the same mistakes. memoir logs it all and hands it off so the next session picks up where the last one left off.
Works with any MCP client: Claude Code, Cursor, Codex, Windsurf, and more.
claude mcp add memoir -s user -- npx -y memoir-mcp
npx -y memoir-mcp
| Tool | Description |
|---|---|
log_attempt | Record something that was tried and its outcome. |
log_blocker | Flag something that's stuck and why. |
resolve_blocker | Mark a blocker as resolved with what fixed it. |
log_decision | Record a design or architecture choice and its rationale. |
end_session | Close the current session with an optional summary. |
| Tool | Description |
|---|---|
get_handoff | Structured summary of the last session -- what was attempted, what's blocked, what was decided. |
get_history | Query past sessions (default: last 3, max 20). |
get_blockers | List unresolved (or resolved) blockers across all sessions. |
Single SQLite file at ~/.memoir/memoir.db. No API keys, no external services.
All limits are configurable via environment variables:
| Variable | Default | Description |
|---|---|---|
MEMOIR_MAX_CONTENT | 500 | Max characters for content fields |
MEMOIR_MAX_OUTCOME | 300 | Max characters for outcome/resolution fields |
MEMOIR_MAX_ENTRIES | 50 | Max entries per session |
MEMOIR_MAX_SESSIONS | 20 | Max sessions per project (rolling) |
Example with custom limits:
claude mcp add memoir -s user -e MEMOIR_MAX_CONTENT=1000 -e MEMOIR_MAX_ENTRIES=100 -- npx -y memoir-mcp
Handoff output uses a compact format to keep context window usage low.
MIT
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y memoir-mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-bighippoman-memoir": {
"command": "npx",
"args": [
"-y",
"memoir-mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referencememoir-mcpnpmio.github.bighippoman/memoir works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.