
Claude Remind Mcp
io.github.emretheus由 GitHub 账号 emretheus 发布v0.1.1更新于 Oct 24, 2026
Search past Claude Code conversations. Local BM25 over JSONL with one-click claude --resume.
发布方自己的服务:Claude Platform Docs
概览
本地 MCP 服务器,为过去的 Claude Code 会话建立索引,让助手搜索、阅读并恢复这些会话。
- 可以做什么
- 用 BM25 排序搜索过去的 Claude Code 对话,可按项目、时间范围和摘要长度过滤,每条结果附带已解决提示和恢复命令
- 读取某条命中消息的完整内容及前后对话,或读取整个会话
- 获取结构化的会话摘要:标题、消息数、使用的工具、涉及的文件、错误数和时间跨度
- 把会话 ID 解析为可直接运行的 claude --resume 命令,并给出工作目录和 git 分支
- 适用场景
- 适合反复排查同一类基础设施、部署或认证问题,希望助手先查历史会话再从头诊断的场景;也适合隔一段时间回到某个项目、想找回之前已解决的方案时使用。
- 运行要求
- 需要 Node.js 20 或更高版本,通过 npx 或全局安装在本机运行。需要会将会话日志写入 ~/.claude/projects/ 的 Claude Code 安装。可选环境变量 CLAUDE_CONFIG_DIR 和 CLAUDE_REMIND_DIR 需为绝对路径,用于覆盖日志与索引位置。无需联网或账号。
安装
在 SourceWeft 中
- 打开 控制台中的 Claude Remind Mcp,将其添加到工作区。
- 为需要使用其工具的对话启用该服务。
Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。
其他 MCP 客户端
参照 仓库 中的启动说明。
README
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.
[npm version] [License: MIT] [TypeScript] [Node.js]
Status: experimental (
v0.1.x). Tool surface is stable; internals may change.
install
From shell:
From any manually configurable mcp.json (Cursor, Windsurf, etc.):
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:
use cases
A few patterns where searching past Claude Code conversation history pays off:
- Recurring infrastructure errors. "We hit
ExpiredTokenExceptionon the staging deploy last month — what was the fix?" Oneremind_searchreturns 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_searchfirst 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 <id>command, plus the originalcwdandgitBranch, 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 tips: prefer concrete terms — exact error strings, tool/library names, file paths. Generic words like auth or docker on their own dilute relevance.
remind_message
Fetch the full text of one message plus optional surrounding turns. Use after remind_search returns a messageUuid you want to read in full.
The matched message is flagged with isFocus: true inside the returned window.
remind_session
Structured summary of a session: title, message count, tool names used, files touched, error count, time span, solved hint, last user message.
remind_resume
Resolves a session id (full or 8-char prefix) to a ready-to-run claude --resume <id> command, plus the session's cwd and git branch. remind_search already returns this on every hit, so prefer that; this tool exists for the case where you only have an id.
how it works
- Streams every JSONL under
~/.claude/projects/line-by-line, with a 1 MB per-line cap and a 50 000 message-per-file cap to keep the indexer bounded. - Skips Claude Code's sidecar entries (
permission-mode,file-history-snapshot,attachment,system-reminder, etc.) so only realuserandassistantturns are indexed. - Redacts well-known secret patterns (API keys, JWTs, private key blocks, env-style assignments) before content enters the index.
- Builds a minisearch BM25 index over the message text plus tool names and project path, and persists it atomically to
~/.claude-remind/. - On startup only files whose
mtimechanged are re-parsed. - For each session derives
hasError,endedCleanly, last user message, and a conservativesolvedHint(likelyonly on explicit positive sentiment or a clean end with no errors;unlikelyonly on explicit negative sentiment;unknownotherwise).
The on-disk index is a single JSON file. It is safe to delete; the next query rebuilds it.
configuration
Both must be absolute paths if set; otherwise the default is used.
privacy
The index file at ~/.claude-remind/index.json is written with mode 0600 and contains the indexed text from your conversations. A built-in regex pass redacts well-known secret formats (OpenAI / Anthropic / GitHub / AWS / Stripe / Google / Slack keys, JWTs, private key blocks, common KEY=value env assignments) before content enters the index. This is best-effort; if you've pasted a custom credential format into a past conversation it may not be caught. Delete ~/.claude-remind/ to wipe the index.
The server runs entirely locally over stdio. It makes no network calls.
development
Scripts:
To point a Claude Code instance at a local checkout:
Smoke-test the MCP handshake from the shell:
Pre-commit runs lint-staged (ESLint + Prettier on staged files) via Husky.
requirements
- Node.js ≥ 20
- A Claude Code installation that writes to
~/.claude/projects/
The package has two runtime dependencies: @modelcontextprotocol/sdk and minisearch. No native modules.
license
来源:README.md,提交 8c510c6
工具
0版本历史
1- v0.1.1最新Sep 16, 2026
评分
已满足适用检查项的 50%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通25 分
请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。
- 已声明认证方式10 分
请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。
- 已列出工具15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分
其他 Claude 集成
Claude Platform Docs
com.claude.platform官方发布者
远程 MCP 服务器,让助手搜索并阅读 Claude 平台文档与 API 参考。

Insta Edits for Claude
由 GitHub 账号 faisalkhanzemi 发布
让 Claude 驱动 Mac 版 Instagram Edits 完整 274 个工具编辑器的桥接服务,并随项目打开同步工具列表。

Claude Checkpoint Mcp
由 GitHub 账号 daniel-munoz 发布
本地 MCP 服务器,把 Claude Code 会话状态保存为项目内的检查点文件,并可重新加载为精简的续接摘要。

Qwen DAP MCP — C/C++ Debugger for Claude Code, Codex & Qwen
由 GitHub 账号 spk-c 发布
通过 GDB、LLDB 和 MCP 为 Claude Code、Codex 和 Qwen 提供 C/C++ 崩溃、挂起和转储调试AI 翻译

AVE for Claude Code — Local Video Editing
由 GitHub 账号 lemberalla 发布
仅适用于 Claude Code 的本地 AVE 时间线编辑与导出。需要现有 AVE 连接。AI 翻译