Persistent 5-level hierarchical memory for AI agents. SQLite-backed, lazy-loaded.
MCPpedia last refreshed this data
io.github.Bumblebiber/hmem-mcp is an MCP server that persistent 5-level hierarchical memory for AI agents. SQLite-backed, lazy-loaded. Its tool list has not been published yet over stdio, sse and http, requires no API key, and scores 86/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"hmem": {
"env": {
"HMEM_AGENT_ID": "DEVELOPER",
"HMEM_PROJECT_DIR": "/home/yourname/.hmem"
},
"args": [
"/absolute/path/to/hmem/dist/mcp-server.js"
],
"command": "/absolute/path/to/node"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Your AI forgets everything between sessions. hmem fixes that.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'hmem' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked hmem against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in data / ai-ml
MCP client bridge: connects to MCP servers and registers their tools on ctx.tools
An autonomous agent that conducts deep research on any data using any LLM providers
1000+ scientific tools for AI scientists: life science, reserach, literature, and more.
Workspace template + MCP server for Claude Code, Codex CLI, Cursor & Windsurf. Multi-agent knowledge engine (ag-refresh / ag-ask) that turns any codebase into a queryable AI assistant.
MCP Security Weekly
Get CVE alerts and security updates for io.github.Bumblebiber/hmem-mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Your AI forgets everything between sessions. hmem fixes that.
One load_project() call. ~3000 tokens. Your agent knows everything important about a project — every past mistake, every decision, every open task — across sessions, devices, and AI providers. No setup per conversation. No "let me re-read the codebase." It just remembers.
AI agent? Skip this file. Read AGENT_SETUP.md — written for you, not for humans.
Naming note (v8.0): This package was briefly published as
its-over-9k(1.x). It is nowhmemagain — pure memory framework, nothing else. Theits-over-9kname lives on as a separate project: the o9k token-efficiency meta-framework, which combines skills/plugins like this one. Related: TIM — hmem's next-generation successor (hypergraph memory, CRDT sync).
hmem is not a note-taking plugin. It's a memory framework for AI agents — a complete infrastructure layer for persistent, portable, token-efficient knowledge that survives session boundaries, device switches, and provider changes.
Four core guarantees:
| Pillar | What it means |
|---|---|
| Token efficiency | 5-level lazy loading — you pay for what you read, never more |
| Portability | Same memory across Claude, Gemini, GPT, local models, any MCP client |
| Efficient storage | Hierarchical tree structure — context scales with depth, not flat append |
| No context waste | Auto-session capture + project briefing = zero re-read overhead |
Every AI session starts from zero. Your agent asks the same questions, makes the same mistakes, contradicts last week's decisions, and wastes 50k tokens loading context it already processed yesterday.
You've tried workarounds — CLAUDE.md files, custom prompts, manually pasting context. They don't scale. You have 10 projects. You switch between 3 devices. You use different AI tools.
You: "Load project"
Agent: [calls load_project("P0048") — 3000 tokens]
Agent: "v1.2.9, TypeScript/SQLite/npm. 3 open bugs, 8 roadmap items.
Last session: rebrand complete, rename_id bug fixed (89 changes).
Next: O-Entry Auto-Purge. What's the focus today?"
That's it. 3000 tokens for a complete project briefing. The agent knows the stack, the architecture, the open bugs, the recent decisions, and exactly where you left off — even if "you" was a different AI on a different machine yesterday.
Level 1 ── One-line summary (always loaded — ~5k tokens for 300+ entries)
Level 2 ── Paragraph detail (loaded on demand)
Level 3 ── Full context (loaded on demand)
Level 4 ── Extended detail (loaded on demand)
Level 5 ── Raw/verbatim data (loaded on demand)
At session start, the agent loads Level 1 summaries — one line per memory. When it needs detail, it drills down. Your 300-entry memory costs 5k tokens to overview. A single project costs ~3000 tokens.
Nothing is summarized away. Level 1 is a compressed view, but Levels 2–5 hold the complete original text, word for word, accessible on demand.
Every conversation is recorded automatically. No "save your work" prompts. No manual checkpoints.
You type → Agent responds → Stop hook fires → Exchange saved to O-entry
→ Linked to active project
→ Haiku auto-titles the session
Switch projects mid-session? The O-entry switches too. Start a new session on a different device? The next agent sees every exchange from every