Kemory

Name: Kemory
Author: SeKondBrainAILabs

by SeKondBrainAILabsversion 0.19.0i★ –iRuns on your computer

Registry nameio.github.SeKondBrainAILabs/kemory

Install

Overview

Description from the maker (original English)

Persistent memory for AI agents: connects MCP clients to your Kemory memory vault

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiVery new↓ 214/wk · ★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Search & AI memory
You need to fill in: KEMORY_API_KEY

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: KEMORY_API_KEY

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "kemory": {
      "command": "npx",
      "args": [
        "-y",
        "kemory",
        "mcp",
        "serve"
      ],
      "env": {
        "KEMORY_API_KEY": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add kemory --env KEMORY_API_KEY=your-value -- npx -y kemory mcp serve

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "kemory": {
      "command": "npx",
      "args": [
        "-y",
        "kemory",
        "mcp",
        "serve"
      ],
      "env": {
        "KEMORY_API_KEY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "kemory": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "kemory",
        "mcp",
        "serve"
      ],
      "env": {
        "KEMORY_API_KEY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

KEMORY_API_KEY secret env
Kemory API key; when unset, mcp serve uses the sign-in from `kemory login`

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account SeKondBrainAILabs, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Search & AI memoryi

More stars than 0% of the other 5684 servers in this category
Published to the registry more recently than 76% of the other 5684 servers in this category
Basic checks equal to or better than 100% of the other 5684 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Kemory safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: KEMORY_API_KEY

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.19.0) reached the registry 12 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Context7, Codebase Memory, Exa

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Context7

Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.

by upstashWidely used↓ 972.7K/wk★ 64.2KUpdated 2 days ago

Computer or cloud

Install

Codebase Memory

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

by DeusDataWidely used↓ 18K/wk★ 48.1KUpdated 22 days ago

Runs on your computer

Install

Exa

Connect AI agents to Exa for web search, content fetching, and multi-step research.

by exa-labsGrowing★ 5.2KUpdated 2 months ago

Runs in the cloud✓ exa.ai

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

kemory

The command-line client for Kemory, a persistent memory vault for AI agents. It signs you in, connects MCP clients such as Claude Code, Codex, Cursor and VS Code to your vault, and runs the MCP bridge they use.

Quick start

You need a Kemory account; sign up at kemory.sekondbrain.ai.

Connect your AI clients. Nothing to install first:

   npx -y kemory connect   # Node.js 18+

uvx kemory connect # or with uv

Your browser opens to sign in. kemory then lists the AI clients on this machine, [ready] or [connected], and asks once: connect every ready client, choose some, or cancel. Claude Code and Grok Build get the Kemory plugin; Codex, Copilot CLI, Cursor, Gemini CLI, OpenCode and VS Code an MCP entry plus automatic memory; the others an MCP entry. Then the connection is checked. A summary lists what is left to do, such as which clients to restart.

Restart the clients it lists. Warp picks the change up without a restart.
Check the setup end to end at any time with kemory doctor.

--dry-run shows what would change without changing anything. In scripts, name the clients instead: --host all, or --host claude-code, --host codex and so on (MCP clients lists them); kemory then asks nothing.

Install

brew install sekondbrainailabs/s9n/kemory

npm install -g kemory uv tool install kemory

Builds exist for macOS (Apple silicon and Intel), Linux (arm64 and x64) and Windows (x64). They are attached to each GitHub release with checksums and build provenance (gh attestation verify --repo SeKondBrainAILabs/kemory-cli). kemory upgrade tells you whether a newer release exists and how to update the copy you installed.

Commands

Command	What it does
`kemory login`	Sign in through your browser (OAuth device flow), or `--local` with an API key
`kemory logout`	Remove the cached sign-in for the selected environment
`kemory whoami`	Show your account, active organisation and teams
`kemory mcp serve`	The stdio MCP bridge an MCP client launches
`kemory hook session-start`, `hook capture`	What a coding agent's hooks run: load your Kemory context when a session starts, save the session when it ends (Hooks)
`kemory connect`	Sign in if needed, wire an MCP client and check the connection
`kemory connect copilot-cloud`	Give GitHub Copilot's cloud agent automatic memory in the current repository (Copilot cloud agent)
`kemory mcp install`	Write the kemory entry into MCP clients (`--host all` for every installed one)
`kemory doctor`	Check sign-in, network, API and MCP clients; `--fix` wires or cleans them
`kemory orgs`, `kemory use`	List your organisations and switch the active one
`kemory remember`, `recall`, `ls`, `show`, `forget`	Store, search, read and delete memories
`kemory ask`	Ask your vault a question and get an answer with its evidence
`kemory namespaces`, `kemory export`	List namespaces, export the whole vault as JSON
`kemory stats`	Recall usage and its token cost; `stats memories` for what is never recalled or rated down
`kemory keys`	Create, rotate, approve, revoke, delete and list API keys for agents
`kemory upgrade`, `telemetry`, `completion`	Check for a newer CLI, set your analytics preference, shell completion

Every command accepts --output json for scripts and agents (stdout then carries only the JSON payload), --quiet, --no-color and --env .

MCP clients

kemory connect --host and kemory mcp install --host connect one client, and --host all connects every client installed on this machine.

For Claude Code and Grok Build they install the Kemory plugin through the client's own claude or grok command. Its hooks save each session to Kemory, and in Claude Code also load your memory when a session starts. Without that command, or for an environment other than prod, they write the MCP entry instead.

For Codex they also add hooks to ~/.codex/hooks.json that load your memory when a session starts and save the session as it goes (Hooks). Codex runs a new hook only after you approve it, so open Codex once and approve them with /hooks. Your other hooks in that file are left as they are.

For Cursor they add the same hooks to ~/.cursor/hooks.json, and for Gemini CLI to the hooks in ~/.gemini/settings.json. Both run them without asking, and your other hooks are left as they are.

For VS Code and the Copilot CLI they write ~/.copilot/hooks/kemory.json, which both run (in VS Code through the chat.useHooks setting, on by default). kemory owns that file and rewrites it on every connect.

For OpenCode they add the opencode-kemory plugin to the plugin list in opencode.json, which OpenCode installs from npm. It does the same: it adds your memory to the system prompt when a session starts and saves your prompts as the session goes. Connected to an environment other than the default, they write the plugin as ~/.config/opencode/plugins/kemory.js instead, which connecting again replaces, so keep your own plugins in other files.

For every other client they write an MCP entry. The entry only starts kemory mcp serve; no token or key is written into the client's config, and everything else in the file is left as it was.

`--host`	Client	Config file (macOS and Linux)
`claude-code`	Claude Code	`~/.claude.json`
`claude-desktop`	Claude Desktop	`~/Library/Application Support/Claude/claude_desktop_config.json`
`codex`	OpenAI Codex	`~/.codex/config.toml`, plus memory hooks in `~/.codex/hooks.json` (or under `$CODEX_HOME`)
`cursor`	Cursor	`~/.cursor/mcp.json`, plus memory hooks in `~/.cursor/hooks.json`
`vscode`	VS Code (Copilot agent mode)	`~/Library/Application Support/Code/User/mcp.json`, `~/.config/Code/User/mcp.json`, plus memory hooks in `~/.copilot/hooks/kemory.json`
`copilot-cli`	GitHub Copilot CLI	`~/.copilot/mcp-config.json` (or under `$COPILOT_HOME`), plus memory hooks in `~/.copilot/hooks/kemory.json`
`copilot-jetbrains`	GitHub Copilot in JetBrains IDEs	`~/.config/github-copilot/intellij/mcp.json` (`%LOCALAPPDATA%\github-copilot\intellij\mcp.json` on Windows)
`junie`	Junie, in JetBrains IDEs and the Junie CLI	`~/.junie/mcp/mcp.json`
`gemini-cli`	Gemini CLI	`~/.gemini/settings.json`, with the memory hooks in the same file
`antigravity`	Google Antigravity	`~/.gemini/config/mcp_config.json`
`windsurf`	Windsurf / Devin Desktop	`~/.config/devin/mcp_config.json`, or `~/.codeium/windsurf/mcp_config.json` for older installs
`cline`	Cline	the VS Code extension's `cline_mcp_settings.json`, or `~/.cline/data/settings/cline_mcp_settings.json`
`kiro`	Kiro	`~/.kiro/settings/mcp.json`
`grok`	Grok CLI	`~/.grok/config.toml`
`continue`	Continue (discontinued in 2026; kept working where it is still installed)	`~/.continue/mcpServers/kemory.json`
`droid`	Factory Droid	`~/.factory/mcp.json`, plus memory hooks in `~/.factory/hooks.json` (or the `hooks` in `~/.factory/settings.json` when you keep yours there)
`zed`	Zed	`~/.config/zed/settings.json` (`%APPDATA%\Zed\settings.json` on Windows), under `context_servers`; your comments in the file are kept
`warp`	Warp	`~/.warp/.mcp.json`
`opencode`	OpenCode	`~/.config/opencode/opencode.json`, plus `opencode-kemory` in its `plugin` list

On Windows the files under Library/Application Support and .config live in %APPDATA% instead, except OpenCode's, which stay in ~\.config\opencode. Grok also reads ~/.claude.json, so the claude-code entry reaches it too.

One connection per client

Each client should reach Kemory one way. Two ways give it every Kemory tool twice, which costs context in every session.

Client	Connect it with
claude.ai, Claude Desktop and Claude mobile	The claude.ai connector, added from the Kemory dashboard
Claude Code and Grok Build	The Kemory plugin, which `kemory connect` installs
Everything else in the table above	`kemory connect --host`

connect and mcp install write nothing for a client that already has Kemory: Claude Code or Grok Build with the Kemory plugin enabled, or Claude Desktop when your account has a claude.ai connector in use. kemory doctor reports a kemory entry that duplicates either one, and kemory doctor --fix removes it.

Claude Desktop rewrites its config file from memory while it runs, which drops an entry added or removed in the meantime. When its config has to change while it is open, connect, mcp install and doctor --fix offer to quit it, make the change and open it again (doctor --fix --yes does so without asking). Run from the terminal inside the Claude app, which would close with it, they offer to open Terminal and continue there instead (macOS).

Copilot cloud agent

GitHub Copilot's cloud agent works in a sandbox where no one signs in, so it reaches Kemory with an API key. Run kemory connect copilot-cloud in the repository it works on, with gh signed in. It:

writes .github/hooks/kemory.json, the hooks that load your memory when a session starts and save the session (commit and push it);
creates an API key for the repository, or a new one on a re-run, and stores it as the repository's Agents secrets KEMORY_API_KEY (for the hooks) and COPILOT_MCP_KEMORY_API_KEY (for the MCP server);
prints the MCP configuration to paste in the repository's Settings → Copilot → MCP servers, and the Kemory host to add to Settings → Copilot → Internet access, so the hooks can reach it.

Without gh it prints the key once, to add as both secrets yourself. The hooks also take KEMORY_API_KEY anywhere else no one signs in.

Exit codes

Scripts and agents can act on why a command failed:

Code	Meaning
0	Success
1	Failure that fits no category below
2	Invalid invocation
3	Not signed in, or the sign-in was rejected — run `kemory login`
4	Kemory could not be reached; nothing ran on the server
5	Signed in but not allowed (403)
6	Not found (404)
7	Conflict with existing state (409)
8	Rate limited (429)
9	Kemory is up but temporarily unavailable (503)

Configuration

Variable	Effect
`KEMORY_ENV`	Environment to use: `prod` (default), `india`, `local`, or one from the environments file
`KEMORY_URL`	Use this Kemory API host instead of the environment's
`KEMORY_OIDC_ISSUER`, `KEMORY_CLI_CLIENT_ID`	Identity provider and client for self-hosted Kemory
`KEMORY_API_KEY`	`mcp serve` authenticates with this key instead of your sign-in
`KEMORY_HTTP_TIMEOUT`	Seconds `mcp serve` waits for Kemory (default 120)
`KEMORY_OUTPUT`	`text` or `json`, like `--output`
`NO_COLOR`	Disable colour

| KEMORY_ACCESSIBLE=1 | Plain numbered p

Only the beginning is shown; read the rest in the repo

Kemory

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Search & AI memoryi

Common questions

Alternatives

Context7

Codebase Memory

Exa

README from the maker

kemory

Quick start

Install

Commands

MCP clients

One connection per client

Copilot cloud agent

Exit codes

Configuration