RMS Memory MCP
Persistent local-first MCP memory server giving AI coding agents a shared Markdown vault with semantic search.
Tested on LinuxKnown vulnerabilities
Use it
Before you install: known vulnerabilities
pickfit found 5 known high or critical vulnerabilities in the packages a fresh install brings (OSV.dev, 3 Nov 2026). Weigh this before you install it.
crates:pulldown-cmark 0.13.5Quadratic parsing of nested image wikilinks with `ENABLE_WIKILINKS` (RUSTSEC-2026-0433, high, fixed in 0.13.6)crates:quick-xml 0.26.0Quadratic run time when checking a start tag for duplicate attribute names (RUSTSEC-2026-0194, high, fixed in 0.41.0)
See 3 more
crates:quick-xml 0.26.0— RUSTSEC-2026-0195 (high), fixed in 0.41.0crates:quinn-proto 0.11.16— RUSTSEC-2026-0340 (high), fixed in 0.11.18crates:quinn-proto 0.11.16— RUSTSEC-2026-0341 (high), fixed in 0.11.17
Linux x86_64
Download install script only
curl -fsSL https://raw.githubusercontent.com/max-ramas/rms-memory-mcp/master/scripts/install.sh -o /tmp/rms-install.shRun install script for rms-memory
bash /tmp/rms-install.sh
Where the README and reality differ
- README: rms-memory config then rms-memory init registers a project
What worked: set global vault path with rms-memory config --vault-path <PATH> before rms-memory init, otherwise init asks to set it first
Check that it works
rms-memory --versionThe output should contain “rms-memory 1.3.2”.
Add it to your agent
claude mcp add rms-memory-mcp -- rms-memory serveJSON for Claude Desktop, Cursor and other clients
{
"mcpServers": {
"rms-memory-mcp": {
"command": "rms-memory",
"args": [
"serve"
]
}
}
}Run rms-memory config --vault-path <vault folder>, then rms-memory init in your project folder, and start the server for your MCP client with rms-memory serve.
What it does
- Keep persistent local memory for AI agentsTested
How to use it
- Set the vault location with
rms-memory config --vault-path <vault folder>. - In your project folder, run
rms-memory init, then check it withrms-memory projects list. - Start the server with
rms-memory serveand connect your MCP client. Call the rms_projects tool to list projects.
- Set the vault location with
- Search memory with hybrid vector searchTested
How to use it
- Save a note with the rms_write tool, giving a project, a path such as <folder>/<note>.md, and the content.
- Call rms_sync for the project to update the index.
- Call rms_search with your query, the project name and a result limit.
- Index source code by meaning in many languagesNot shown working
How far pickfit got
Linux x86_64
- Installs
- Connects
- 2 of 3 features work
- Works offline
macOS and Windows: the project says it runs there; pickfit hasn’t tried it.
Good for
- search Markdown project memory
- persist architectural decisions and rules
- read a memory document by path
- run vault health diagnostics
- export vault as llms.txt
How pickfit tested it
Each run starts from a clean machine and follows the steps above. How pickfit verifies
Linux x86_64
An MCP client called one of its tools
- Replayed from scratch
- Works offline
- Checked on 30 Oct 2026
- Version 1.3.2
An MCP client handshake over stdio listed 19 tools, and a call to rms_projects returned a result.
Differences the test machine hit
- README: curl -fsSL .../scripts/install.sh | bash
In the test: install.sh downloads a prebuilt binary tarball rms_memory_mcp_<version>_<target>.tar.gz which cannot be read as text before running - README: curl ... install.sh | bash installs binary
In the test: install.sh automatically runs rms-memory install at the end (found no IDE configs here)