MCP SERVER · OFFICIAL PROJECTSave what a session worked out at a keypath, find it again by meaning or by path, and read back every version a value has held — deletes are tombstones, so nothing is actually lost.
LABSCO SUMMARY
A deleted keypath comes back by setting a new value at the same path, and a deleted project comes back by creating one with the same id, with the history intact in both cases. The two save paths are split on purpose and each says what it is not for: memstate_remember takes text with several facts in it and does the structuring, while memstate_set is only for a single short value at a keypath you already know. Reads can be pinned to a point in the past through at_revision, so what an agent saw at the time is reconstructable rather than overwritten by what is true now.
A versioned memory store addressed by project and keypath, with semantic search across the contents and full history behind every value.
MEMSTATE_API_KEY, and a project_id for anything beyond listing the projects themselves.
One command plus a key — claude mcp add memstate npx @memstate/mcp -e MEMSTATE_API_KEY=<YOUR_MEMSTATE_API_KEY>
USE CASES
The project tree can be browsed when you know where things live, and searched by meaning when you do not. Content length is capped on the way back so a broad browse does not empty the context window.
Text with several facts in it goes in whole and the server extracts the keypaths and detects conflicts; a single short value at a keypath you already know goes through memstate_set instead.
Every keypath keeps its versions, so a wrong assumption can be traced back to the moment it was written and the earlier value read out rather than reconstructed.
Deletion is a tombstone that preserves the history, and the same keypath comes back the moment a new value is set at it. A whole project can be tombstoned the same way and restored by recreating it under the same id.
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
memstate_deleteSoft-delete a memory by keypath. Creates a tombstone version preserving full history. The memory can be un-deleted by setting a new value at the same keypath.
USE THIS WHEN: You need to remove outdated or incorrect memories, clean up a keypath subtree, or mark memories as no longer relevant. NOT FOR: Updating content (use memstate_set or memstate_remember to overwrite with new content instead).
memstate_delete_projectSoft-delete an entire project and all its memories. Creates tombstone versions for every memory, preserving full history. The project is hidden from listings but can be restored by creating a new project with the same ID.
USE THIS WHEN: You want to remove all memories for a project, e.g. cleaning up test data or decommissioning a project.
memstate_delete_project(project_id="old-project")
All memories get individual tombstone versions. History is preserved via memstate_history.
memstate_getBrowse and retrieve memories. Use BEFORE starting tasks to fetch existing knowledge.
USE THIS WHEN: You need to read what's already stored — list projects, browse a project tree, or get content at a keypath. NOT FOR: Saving new content (use memstate_remember for markdown/summaries, memstate_set for one keypath value).
memstate_historyView version history for a keypath or memory chain. Use when you need to see how a value changed over time.
USE THIS WHEN: Debugging past state, auditing changes, or recovering a previous value. NOT FOR: Reading current content (use memstate_get) or saving (use memstate_remember or memstate_set).
memstate_history(project_id="myapp", keypath="config.database.port")
Returns all versions with timestamps and version numbers; latest is marked is_latest=true. Use version numbers with memstate_get(at_revision=N) to time-travel to any past state.
memstate_rememberSave markdown, task summaries, or any text. Server extracts keypaths and creates structured memories automatically. This is the PREFERRED way to save information.
USE THIS WHEN: Saving task summaries, meeting notes, docs, or any text with multiple facts. The server handles organization, conflict detection, and versioning. NOT FOR: Setting one specific keypath to a short value (e.g. config.port = "8080") — use memstate_set for that.
memstate_searchFind memories by meaning (semantic search). Use BEFORE starting tasks when you don't know the exact keypath.
USE THIS WHEN: You want to find relevant memories by topic or meaning, not by exact keypath. NOT FOR: Saving content (use memstate_remember for markdown/summaries, memstate_set for one keypath value).
memstate_search(query="how is authentication configured", project_id="myapp") memstate_search(query="database connection settings", project_id="myapp")
Returns summaries with similarity scores.
memstate_setSet one keypath to a short value. Only for simple key=value facts like config, status, or version numbers.
USE THIS WHEN: You need to store ONE specific value at a known keypath (e.g. a port number, a status flag, a version string). NOT FOR: Task summaries, markdown, or text with multiple facts — use memstate_remember instead.
BEFORE YOU INSTALL
7 tools when we connected. memstate_remember handles most writes. MEMSTATE_API_KEY=your_key npx @memstate/mcp --test prints the tools available to your key.
npx on PATH
CONTEXT COST
Rated by the size of the 7 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
claude mcp add memstate npx @memstate/mcp -e MEMSTATE_API_KEY=<YOUR_MEMSTATE_API_KEY>{
"mcpServers": {
"memstate": {
"command": "npx",
"args": [
"-y",
"@memstate/mcp"
],
"env": {
"MEMSTATE_API_KEY": "<YOUR_MEMSTATE_API_KEY>"
}
}
}
}MCP servers
catfish-1234
oleksiijko
kraklabs
Thezenmonster