Melchizedek
Add durable, offline, single-file memory with hybrid search so Claude Code remembers project context across sessions without a cloud vector DB.
Overview
Melchizedek is a Build-phase MCP server that provides Claude Code with persistent offline memory and hybrid search stored in a single file.
What is this MCP server?
- Persistent memory designed for Claude Code workflows
- Offline operation—no mandatory remote memory service in the manifest
- Single-file storage model for simpler backup and portability
- Hybrid search across stored memories
- npm package melchizedek v1.0.2 with stdio MCP transport
- Manifest version 1.0.2
- npm identifier melchizedek with stdio transport
- No required environment variables in published server.schema.json
Community signal: 7 GitHub stars.
What problem does it solve?
Coding agents forget prior session context, forcing you to repeat architecture decisions and project facts every new chat.
Who is it for?
Solo Claude Code users who want private, offline continuity and simple single-file backups of agent memory.
Skip if: Teams needing shared org-wide knowledge graphs, real-time collaboration memory, or compliance-reviewed hosted retention.
What do I get? / Deliverables
Your agent can write and retrieve durable local memories so multi-day solo builds stay consistent without a cloud memory stack.
- Stored memory entries the agent can update across sessions
- Hybrid-search recall of prior facts and decisions in new chats
- Portable offline memory file you can back up with your repo or dotfiles
Recommended MCP Servers
Journey fit
Persistent agent memory is part of shaping how you build with coding agents—tooling that sits alongside skills and MCP during product development. Melchizedek is explicitly agent-tooling for Claude Code: it extends the agent runtime with recall, not app frontend or deployment infra.
How it compares
Local hybrid-search memory MCP server, not a hosted RAG platform or a brainstorming methodology skill.
Common Questions / FAQ
Who is io.github.louis49/melchizedek for?
It is for Claude Code users and solo developers who want persistent agent memory that works offline and stores state in one portable file.
When should I use io.github.louis49/melchizedek?
Use it when long-running projects outgrow chat context limits and you want the agent to recall prior decisions locally instead of pasting summaries each session.
How do I add io.github.louis49/melchizedek to my agent?
Install the npm package melchizedek, add a stdio MCP server entry pointing at that binary in Claude Code (or another MCP client), restart the client, and invoke the memory tools from your workflow.