remindb
Token-efficient agentic memory database. Mounts remindb as an MCP server, exposing the Memory* tool suite over a compiled SQLite view of the workspace.
pinned to #977b31cupdated 2 weeks ago
Ask your AI client: “install plugins/remindb”.
Requires the metahub MCP server installed in your client. Set up MCP.
mh install plugins/remindbmetahub onboarded this repo on the author's behalf.
If you own github.com/radimsem/remindb on GitHub, claim the listing to take over publishing. Your claim preserves the existing eval history and badges; only the curator label is replaced with verified-publisher on your next publish.
Stars
121
Last commit
2 weeks ago
Latest release
published
- #agent-memory
- #ai-agents
- #ast
- #claude-code
- #cli
- #codex
- #developer-tools
- #fts5
- #gemini-cli
- #golang
- #knowledge-base
- #llm-tool
- #mcp
- #mcp-server
- #model-context-protocol
- #openclaw
- #opencode
- #sqlite
- #token-efficiency
Evaluation report
WarningsAutomated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.977b31c· 2 weeks ago
Kind-specific
31Plugin: manifest fields complete
Plugin: bundled artifacts presentwarn
Couldn't find a skills/ subdir or an MCP server config inside the plugin
A plugin is most useful when it bundles ≥ 1 skill or an MCP server.
Plugin: bundle shape
empty bundle
Plugin: manifest location
manifest at plugin.json
Release history
1- releasecurrent977b31cwarn2 weeks ago
Contents
Drops remindb into Claude Code as an MCP server. The agent picks up the full Memory* tool suite, backed by a compiled SQLite view of whatever workspace you point it at.
How it works
Claude Code loads .claude-plugin/plugin.json as the plugin manifest and merges .mcp.json into its effective MCP server list. When Claude Code starts with the plugin enabled, it spawns remindb serve over stdio. All the tool logic lives in the Go binary; the plugin is a thin wrapper.
Tools are namespaced, so MemoryFetch shows up as remindb__MemoryFetch in the tool list.
Installation
Setup is config-first and wizard-driven: install the binary and skills, run /remindb-setup before the plugin is attached (it authors .remindb/, compiles, and wires the env for you), then enable the plugin and restart. You don't hand-compile or hand-edit config — the wizard owns that.
1. Install the remindb binary
It needs to be on $PATH:
curl -fsSL https://raw.githubusercontent.com/radimsem/remindb/main/install.sh | bash
On Windows:
iwr -useb https://raw.githubusercontent.com/radimsem/remindb/main/install.ps1 | iex
Verify: remindb --version.
2. Install the companion skills
This pulls the remindb-setup wizard plus the remind (read) and memorize (write) skills:
npx skills@latest add radimsem/remindb/skills -a claude-code
Refresh them later — independent of remindb update — with npx skills@latest update.
3. Run the setup wizard
In a Claude Code session, invoke the wizard as a slash command:
/remindb-setup # interactive — walks each choice
/remindb-setup automode # hands-off — infers the whole setup
Running before the plugin is attached is intended: the wizard detects the host, authors .remindb/ (ignore/pinned/temperatures.json/config.json) before compiling, runs remindb compile, offers to seed adjacent context (this project's CLAUDE.md, in-repo README.md), and wires the MCP env. A natural source for Claude Code is its own cross-project memory at ~/.claude/projects/ — the wizard will suggest it.
4. Enable the plugin
/plugin marketplace add radimsem/remindb
/plugin install remindb@remindb
Or, if you're hacking on the plugin, a local checkout: claude --plugin-dir ./plugins/claude-code.
5. Restart and verify
Start a new session (so the freshly-wired env and plugin take effect), then confirm the server is connected:
/mcp
You should see remindb with the full Memory* tool suite. Re-run /remindb-setup — now that the server is attached, it runs its verify pass (MemoryStats + remindb://doctor).
Durable env
remindb serve reads REMINDB_DB and REMINDB_SOURCE as fallbacks for its --db/--source flags, and the bundled .mcp.json declares both as ${VAR} passthroughs. For a marketplace install the manifest lives in the plugin cache under ~/.claude/plugins/ and is overwritten on every update, so the wizard can't durably write it — it emits a shell-export snippet instead, which you add to ~/.bashrc / ~/.zshrc / your fish config:
export REMINDB_DB=$HOME/.cache/remindb/claude.db
export REMINDB_SOURCE=$HOME/.claude/projects
Launch Claude Code from that shell. For a local checkout (--plugin-dir) you own the file, so the wizard writes the paths straight into the env block of .mcp.json. Either way, don't inject a same-named server into user-scope ~/.claude.json — Claude Code replaces the plugin's bundled entry rather than merging it, dropping the plugin wiring entirely.
Tools exposed
The plugin surfaces the full remindb Memory* tool suite under the remindb__ namespace. See the main README for the canonical tool list and per-tool token-savings benchmarks.
License
MIT — same as remindb.
Reviews
No reviews yet. Be the first.
Related
before-you-build
Production-ready workflow orchestration with 91 marketplace plugins, 199 local specialized agents, and 162 local skills - optimized for granular installation and minimal token usage
manifest-dev-tools
Tools for working with prompts and PRs alongside the manifest workflow. Collaborative PR walkthroughs, autonomous PR review with per-comment verification, author-side PR babysitting via manifest-dev, gap-calibrated prompt engineering, cross-boundary context handoff, and incremental teaching for session work.
plugin-template
A template for creating new Claude Code plugins
mh install plugins/remindb