store_memoryLABSCO SUMMARY
The list-then-fetch split is the design decision that matters.
Returning titles and timestamps from the list call, and bodies only on request, is what keeps a growing memory store from eating the context window every time the assistant checks what it knows. The web interface earns its place too: memory that only an assistant can read is memory you cannot correct. If several assistants are open at once they share one server and one database, so a note written in one shows up in the other.
What it is
A memory server that keeps titled notes in a local database and gives the assistant four tools to work with them, plus a fifth that opens a browser interface for editing them yourself. Storing is deliberately two-step: the assistant asks for a title first, then the content.
What you get
store_memorysaves a new note, requiring both a title and contentlist_memory_titlesreturns the titles and timestamps only — not the bodies — so listing stays cheap in contextget_memory_by_titlepulls the full content of one note once you know which one you wantdelete_memoryremoves a noteopen_memory_webstarts the local web interface and opens a browser at it, triggered by asking the assistant to open memory- The web interface adds full-text search across titles and content, drag-to-reorder, and copy, edit and delete on each card
- A single-instance design: several assistants connecting at once share one running server and one database rather than starting rival copies
Requirements
Node.js 16.0.0 or higher. Clone the repository, run npm install and npm run init-db to create the database, then point the client at start-mcp.js with the project directory as cwd. The published package is simple-memory-mcp, version 1.3.0. The web interface defaults to http://localhost:8011 and moves to another port automatically if that one is taken.
Setup effort
Build from source — git clone https://github.com/eragonht1/simple-memory-mcp.git
USE CASES
Keeping project context between sessions
Save the decisions and setup notes under clear titles and pull them back by name later.
Seeing what is stored without loading it all
List the titles first, then fetch only the note you actually need.
Fixing a note the assistant got wrong
Open the web interface and edit or delete it directly instead of talking the assistant into a correction.
Sharing memory between two assistants
Both connect to the same running server, so what one saves the other can read.
5 tools
Listed in project docs. Your client may show a different list.
list_memory_titlesget_memory_by_titledelete_memoryopen_memory_webBEFORE YOU INSTALL
What to know first
Tools you get
5 tools named in the project's documentation.
Requires
- node on PATH
- Node.js 16.0.0 or higher
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
You clone this one yourself.
Server setup
git clone https://github.com/eragonht1/simple-memory-mcp.git
cd simple-memory-mcp
npm install
npm run init-dbMCP Clients
Any MCP client
{
"mcpServers": {
"simple-memory": {
"command": "node",
"args": [
"<YOUR_PATH_TO_SIMPLE_MEMORY_MCP>/start-mcp.js"
],
"cwd": "<YOUR_PATH_TO_SIMPLE_MEMORY_MCP>"
}
}
}