Claude Remind MCP server
io.github.emretheus/claude-remind-mcp·v0.1.1·1 starsSearch past Claude Code conversations. Local BM25 over JSONL with one-click claude --resume.
1 stars45 downloads/wk
Reviews
Write oneNobody has reviewed Claude Remind yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Claude Remind tools (4)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
remind_messageFetch the full text of a specific past message, plus optional surrounding turns. Returns up to ~10 KB; the matched message is flagged with `isFocus: true` inside the returned window. When to use: only after `remind_search` returns a `messageUuid` whose snippet looks promising but is truncated. Don't call this for every search hit — pick the one or two most relevant first. If you want a structural
remind_resumeResolve a (full or 8-char prefix) session id into a ready-to-run `claude --resume <id>` command, plus the session's cwd and git branch. When to use: only when you already have a sessionId in hand and need just the resume command. `remind_search` already returns `resumeCommand` on every hit, so prefer that. This tool exists for cases where the user pastes a bare sessionId or a previous tool flow st
remind_searchSearch past Claude Code sessions for solutions to recurring problems. Returns BM25-ranked hits with a snippet, a `solvedHint`, a `messageUuid`, and a ready-to-paste `claude --resume <id>` command. When to use: at the start of a task to check for prior work on the same codebase; or when the user mentions an error, tool, or feature they may have already solved. One call is usually enough — only re-c
remind_sessionGet a structured summary of one past session: title, message count, tool names used, files touched, error count, time span, solved hint, and the last user message. Cheap (~1 KB). When to use: when a `remind_search` hit looks relevant and you need the bigger picture (was this session productive? which tools/files were involved?) before drilling into specific messages. Requires a `sessionId` — the 8
Public scan report
scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it
- Code scan33 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 139 days ago8/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Claude Remind compares
Against every graded Web search MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 82/100
- higher than 68% of 3,470 Web search servers
- Tools
- 4
- the typical Web search server has 5
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- GitHub stars
- 1
- more than 55% of 1,786 Web search servers
- Downloads a week
- 45
- more than 31% of 827 Web search servers with a package
What its tools let an agent do: 4 read
Install Claude Remind in Claude Code, Cursor or VS Code
Runs npx -y claude-remind-mcp on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add claude-remind-mcp -- npx -y claude-remind-mcp
What the publisher says
From the Claude Remind repository's README, as published. We do not edit it. Read it on GitHub
claude-remind-mcp
A Model Context Protocol (MCP) server that searches your local Claude Code conversation history. It indexes every past session under ~/.claude/projects/ with BM25, redacts secrets, and lets the running Claude agent recall and resume solutions you've already worked out — without re-explaining the problem from scratch.
If you've ever caught yourself solving the same Docker, deployment, or auth bug twice in a month, this is for you. The package is local-only (no network calls), pure-JS (no native modules), and ships as a single npx-installable binary.
Status: experimental (v0.1.x). Tool surface is stable; internals may change.
install
From shell:
claude mcp add claude-remind -- npx -y claude-remind-mcpFrom any manually configurable mcp.json (Cursor, Windsurf, etc.):
{
"mcpServers": {
"claude-remind": {
"command": "npx",
"args": ["-y", "claude-remind-mcp"]
}
}
}No model downloads, no daemons, no database. The first query builds an index from ~/.claude/projects/ (a few seconds for a typical history) and persists it to ~/.claude-remind/. Subsequent queries reuse the index and only re-parse files whose mtime changed.
If npx resolves the wrong package, force resolution:
npm install -g claude-remind-mcpuse cases
A few patterns where searching past Claude Code conversation history pays off:
- Recurring infrastructure errors. "We hit ExpiredTokenException on the staging deploy last month — what was the fix?" One remind_search returns the exact session, the resolved snippet, and the resume command.
- Cross-project knowledge. "How did I configure BuildKit cache on the other Coolify project?" The index spans every project under ~/.claude/projects/, so solutions from project A surface when you're working in project B.
- Onboarding into your own past work. Coming back to a repo after weeks? Search for "Cognito", "RunPod", "tailwind config" and read the latest session summary instead of grepping through code.
- Avoiding redundant deep-dives. Before Claude burns 10k tokens diagnosing a problem from scratch, it can call remind_search first and see if you already solved it. The default response is ~1.5 KB.
- Resuming where you left off. Every search result includes a ready-to-paste claude --resume command, plus the original cwd and gitBranch, so jumping back into a half-finished thread is one paste away.
tools
Four tools, designed to compose: search → read → resume.
remind_search
BM25 search over past messages. Returns ranked hits with a snippet, a solvedHint, a messageUuid, and a ready-to-paste claude --resume command.
{
query: string;
project?: string; // substring of cwd, e.g. "my-app"
limit?: number; // 1–50, default 5
sinceDays?: number; // age filter
format?: "compact" | "detailed" | "full"; // 400 / 1000 / 2000-char snippet
}Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Claude Remind: common questions
- Is Claude Remind MCP server safe?
- Mostly: it is graded B (82/100). Read the Claude Remind safety report
- How do I install Claude Remind?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Claude Remind need an API key?
- No secret keys are declared. It reads 2 settings from the environment.
- Is Claude Remind maintained?
- The last commit was 177 days ago (2026-05-11). The latest release is v0.1.1.
- What can I use instead of Claude Remind?
- Servers from other publishers that do the same job: ThoughtDAG MCP server, Ref Tools MCP server and Abap Adt Ro MCP server.
- How does Claude Remind compare with other Web search MCP servers?
- safety score 82/100 (higher than 68% of 3,470 Web search servers); tools 4 (the typical Web search server has 5); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.
Alternatives to Claude Remind
Same job from other publishers: the closest match first, then the best rated.
- ThoughtDAGSearch local AI conversations by file or phrase and recall source turns. Four read-only tools.not reviewedEstablishedA
- Ref ToolsToken-efficient search for coding agents over public and private documentation.not reviewedEstablishedA
- Abap Adt RoRead-only MCP server for SAP ABAP ADT over HTTP, RFC or SNC: the readonly, system and search toolsnot reviewedEstablishedA
- MinutesThe private, owned conversation-memory layer for AI. Record, transcribe, and search every meeting.not reviewedEstablishedA
- Silica CoreRetrieval over the folder the session opened: files, search, read, code_pack, write_note.not reviewedGrowingA