claude-remind-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLAUDE_CONFIG_DIR | No | Where Claude Code stores its logs. Default: ~/.claude | ~/.claude |
| CLAUDE_REMIND_DIR | No | Where the index is persisted. Default: ~/.claude-remind | ~/.claude-remind |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| remind_searchA | Search past Claude Code sessions for solutions to recurring problems. Returns BM25-ranked hits with a snippet, a 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-call with a different query if the first returned no useful hits. Query tips: use specific concrete terms — exact error strings ( Cost: ~1–2 KB per call at default (5 hits, 1000-char snippets). Use |
| remind_messageA | Fetch the full text of a specific past message, plus optional surrounding turns. Returns up to ~10 KB; the matched message is flagged with When to use: only after To read the entire session, omit |
| remind_sessionA | Get 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_resumeA | Resolve a (full or 8-char prefix) session id into a ready-to-run When to use: only when you already have a sessionId in hand and need just the resume command. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clear, distinct purpose: searching sessions, fetching full messages, summarizing session metadata, and providing resume commands. No overlap in functionality.
All tools follow a consistent 'remind_<verb>' pattern with snake_case, making the action and target clear (e.g., remind_search, remind_message).
Four tools cover the core workflow (search, read, summarize, resume) without unnecessary extras. The count is perfectly scoped for the domain.
The set covers the full lifecycle of retrieving past session information: searching, viewing details, getting summaries, and obtaining resume commands. There are no obvious missing operations.