Wax MCP
wax
Local memory for agents in a single .wax file with no account and no cloud database. The npm installer downloads binaries once. Version 0.1.x
- 804 ★ on the repository
- Last commit
- Apache-2.0
Extended access
Why this level
- Version 0.1.x, the memory format may change
- The installer downloads binaries
Install
- Works in
Manual install
npx -y waxmcp@latest installThe installer downloads ready binaries once. For Hermes: npx -y waxmcp@latest install-hermes-plugin.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Version 0.1.x, the memory format may change
- The installer downloads binaries
This is third-party code. Review the repository files before installing.
What it does
Wax keeps agent memory locally in a single `.wax` file: no account or cloud database is needed and memory stays on the device. Installation: `npx -y waxmcp@latest install`, and the npm installer downloads ready binaries once. For the Hermes agent there is a separate plugin (`install-hermes-plugin`). Written in Swift, version waxmcp v0.1.48 from 24.09.2026, Apache-2.0 license. The project is early, version 0.1.x.
Who it is for. For developers who need portable agent memory in a single file with no cloud.
Good fit when
- You need local agent memory in a single file
- You need memory with no account and no cloud
- You need a memory plugin for Hermes
Not a fit when
- You need a mature version: it is 0.1.x now
- You cannot download ready binaries with an installer
Example request
Remember that we use pnpm in this project and recall it in a new sessionMCP
- Transport
- stdio, http
- Authentication
- not required
Limitations
The npm installer downloads built binaries and installs them on your machine, so access is extended. Version 0.1.x, so the memory file format may change. Keep a copy of the .wax file: it is the only memory storage.
How to disable. Remove the server entry from the client and the installed binaries. Delete the .wax file separately if the memory is no longer needed.
FAQ
Where is the memory stored?
In a single local .wax file on your device.
Is an account needed?
No, neither an account nor a cloud database is needed.
How do I install it?
npx -y waxmcp@latest install.
Discussion
No questions or reviews yet.
Related
MCP serversA local-first MCP memory server for agents: session history, codebase index and a concept graph in one SQLite database
Local persistent memory for coding agents: hooks record every session, and Claude Code, Codex or Cursor recall past decisions through 54 MCP tools
iai-memory
iai-memory (Personal Memory Engine)
A local long-term memory MCP server for agents: keeps conversations verbatim and returns the right context at the start of a session
A self-hosted MCP server for long-term agent memory: structured records, versioned rollback and a visual dashboard
Long-term memory for AI agents: Markdown files as the source of truth, a SQLite index as a cache, shared by Claude Code, Codex and others
Long-term memory for agents: a remote MCP server, plugins for Claude Code, Cursor and Codex, and an API for your own apps
Comparison with similar tools
Entries that share the main search query, and how they differ.
| Entry | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Wax (this entry) | no | not required | 804 | |
| Hippo Memory | no | not required | 776 | memory in SQLite with markdown mirrors and a Slack connector |
| deja-vu | no | 1,194 | search across saved agent sessions with no model | |
| agent-memory | no | 3,398 | long-term memory on Markdown files with a SQLite index |
README in short
The README describes local agent memory in a single .wax file, installation through npx and a plugin for Hermes. Apache-2.0 license.