Mooncite

Mooncite lets coding agents recover past context without asking you to explain it again. It searches authorized Pi, OMP, Claude Code, Codex, and ChatGPT history stored on this machine. Before an agent relies on a result, `mooncite_inspect` checks the citation against the original file. That confirms where the text came from. It does not prove the text is still true.

Mooncite was formerly Claude Memory MCP. The repository keeps its old `claude-memory-mcp` URL.

flowchart LR
    H[Human] -->|installs| M[Mooncite]
    A[Coding agentPi, OMP, Codex, Claude Code] -->|recall and inspect| M
    M -->|reads only| S[Local historyPi, OMP, Claude Code, Codex, ChatGPT]
    M  I[(Search index)]
    M -.-> L[(Optional learned memory)]
    M -->|cited context| A

Install

Mooncite requires Linux with procfs, Node.js 24 or newer, `npm`, and access to GitHub.

npx --yes github:WhenMoon-afk/claude-memory-mcp#v4.0.5 install

Tagged v4.0.5 is the current stable release. After installation, check the launcher. Then fully restart or reload each client whose registration is `exact`:

"$HOME/.local/bin/mooncite" status

The installer configures available Pi, OMP, Codex, and Claude Code clients. ChatGPT is a source, not a client. See operations for the prerelease, source setup, ChatGPT exports, removal commands, and quick fixes.

First search

Recall runs inside a configured client. It is not a shell command. Give the agent one distinctive phrase:

> Call `mooncite_recall` with "". Start without a scope. If it returns a candidate, inspect that candidate's `evidence_id` with `mooncite_inspect`. Treat `verified` as proof that the cited text still matches its source file. It does not prove the text is true.

Mooncite exposes exactly three evidence tools by default:

• `mooncite_recall` searches bounded local evidence.
• `mooncite_inspect` checks a locator against current source bytes.
• `mooncite_status` reports coverage and health without transcript text.

Learned memory is separate and off by default. Enabling it adds four `mooncite_memory_*` tools. Those tools store agent-authored interpretations in a separate database.

Read next

• Agent workflow tells an agent when to recall, narrow, inspect, and recover.
• MCP protocol lists exact tool inputs, outcomes, and learned-memory operations.
• Operations covers install, source configuration, status, rebuild, disable, uninstall, and purge.
• Architecture explains the engine, index, clients, and learned-memory boundary.
• Security explains source containment, local data handling, and deletion limits.

Mooncite never writes source history. Text returned through MCP becomes model context and is subject to that model provider's data handling.