Kemory runs on your own machine — the client starts it, so there is no endpoint to ping. 435 installs a week from npm. Last commit 28 Oct 2026.
Persistent memory for AI agents: connects MCP clients to your Kemory memory vault
We read the source, 5 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.
const archivePath = path.join(tmp, asset);
Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.
insert := "\n " + string(quotedKey) + ": {" + line + "\n }"
if len(root) > 0 {
const child = execFile(
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 kemory -- npx -y kemory
{
"mcpServers": {
"kemory": {
"command": "npx",
"args": [
"-y",
"kemory"
]
}
}
}
[mcp_servers.kemory]
command = "npx"
args = ["-y", "kemory"]
{
"mcpServers": {
"kemory": {
"command": "npx",
"args": [
"-y",
"kemory"
]
}
}
}
{
"servers": {
"kemory": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"kemory"
]
}
}
}
Optional settings from the registry entry, left out of the block above:
KEMORY_API_KEY (Kemory API key; when unset, mcp serve uses the sign-in from `kemory login`).
Long-term memory for AI agents — your Obsidian vault as searchable persistent memory.
Local-first persistent memory for coding agents and MCP clients.
MCP server for persistent, searchable memory for AI agents.
Local-first persistent memory MCP server for AI coding agents.
Persistent memory for AI assistants — one shared, OAuth-secured vault for every MCP client.
Shared, persistent memory for AI agents — works with Claude, Kiro, Cursor, or any MCP client.
Shared persistent memory for AI agents to read, verify, continue, and connect knowledge.
Local-first persistent memory for AI coding agents.
Answers built from our own checks of this server.