Mnemosyne OS runs on your own machine — the client starts it, so there is no endpoint to ping. 267 installs a week from npm. Last commit 1 Nov 2026.
Memory the human governs, on their own machine, plus what other coding agents here wrote.
We read the source, 1 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
renderChronicle(path.join(dir, selected));
const child = spawn(process.execPath, [daemonPath], {
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add mcp -- npx -y @mnemosyne_os/mcp
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@mnemosyne_os/mcp"
]
}
}
}
[mcp_servers.mcp]
command = "npx"
args = ["-y", "@mnemosyne_os/mcp"]
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@mnemosyne_os/mcp"
]
}
}
}
{
"servers": {
"mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@mnemosyne_os/mcp"
]
}
}
}
Optional settings from the registry entry, left out of the block above:
MNEMO_DEFAULT_VAULT (Vault used when a call does not name one. The vaults are the user's own domains of memory (code, notes, journal); nothing outside the granted list is reachable), MNEMO_VAULTS (Comma-separated list of vaults this server may reach. Narrow it: a vault left out here cannot be read even by mistake), MNEMO_SDK_PORT (Port of the local Mnemosyne OS SDK server the desktop app listens on).
Local-first long-term memory for AI coding agents. Stored on your own machine.
Private, self-describing memory for agents: one house per customer, on a machine of its own.
Local MCP memory for coding agents. SQLite on your machine — preferences persist across chats.
Memory for coding agents: the decisions, the dead ends, and where the last session stopped.
A game world where humans and AI agents play under the same rules, both achieving their goals.
Team memory for AI coding agents and code reviews, reviewed by humans and served over MCP.
Code graph and project memory for coding agents, cited to exact files and lines, on your machine.
Skills, agents and memory in the cloud, plus a gateway to your other MCP servers.
Answers built from our own checks of this server.