S
stoneskin/open-memex
Local-first memory layer for AI coding agents — Markdown as source of truth, MCP server + CLI, human-reviewed capture, team knowledge via git PRs.
no SECURITY.md
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
Install & config
- Copy the command above
- Paste it as one entry under
mcpServersinclaude_desktop_config.json— local servers take command + args (example: clients) - Restart your client
Client config (built from the install command this repo gives)
{
"mcpServers": {
"stoneskin-open-memex": {
"command": "npx",
"args": ["-y", "open-memex"]
}
}
}Parsed from the README we fetched on 2026-10-26; we have not executed it.
command/args come from the install command the repository states. When it is ambiguous, the project README wins.
VS Code (.vscode/mcp.json - the key is servers)
{
"servers": {
"stoneskin-open-memex": {
"command": "npx",
"args": ["-y", "open-memex"]
}
}
}Same server, but VS Code keeps it under <code>servers</code>.
Claude Code (command line)
claude mcp add --transport stdio stoneskin-open-memex -- npx -y open-memex
Claude Code does not read a config file; add the server with this command.
Key names differ by client: Clients & CLI
- Star count
- 6 ★ · stoneskin/open-memex · read from the GitHub search API · (checked 2026-11-13 20:00:50)
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-10-23 · last seen 2026-11-14 · seen 26× · listed by 23 sources
- Score
- score 2,300 · 6 ★ · 23 sources · mcp
- Install
npx -y open-memex
FAQ (answers come from our records)
How do I install it?
The repository provides this install command:
npx -y open-memex. It comes from the repository itself; we cannot guarantee it runs as-is in your client.Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
stoneskin/open-memex；first catalogued 2026-10-23；last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.# open-memex
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
> Persistent memory for your AI coding agents — on your machine, in plain Markdown, shared by every tool you code with.
中文文档
Every AI coding session starts from zero: you re-explain the project, the agent
rediscovers the same gotchas, and yesterday's decisions vanish when the chat
ends. open-memex gives your agents a memory that survives the session. Say
"remember: we deploy on Fridays" once, and next week Copilot, Cursor, opencode,
or Claude Code already knows — because they all read and write the same local
memory on your machine.
Free and open source (Apache-2.0). No account, no cloud, no telemetry —
everything lives on your machine, in files you can open and edit.
Local-first: memories are plain Markdown files (the source of truth) with
a rebuildable SQLite keyword index. Nothing leaves your machine unless you
explicitly share it.
One memory, every agent: wire up several editors with one command; they
share the same memory instead of keeping separate silos.
Precise synonym search: ship finds deploy, 单点登录 finds SSO —
a curated multilingual map of equivalents is indexed with every memory at
write time, so no related wording misses the right answer. Deterministic
and auditable, no embedding model required.
New here? This README takes you from install to a working memory in about a
minute. The concept guide explains the mental model in
depth once you're up and running.
## Contents
Quick start
Core concepts
Which editors, which features
Installation
Setting up your editor
What init changes on your machine
Capture: how memories get saved
Tools the agent gets
Memory types
Team workflow: sharing memories through Git
Retrieval: how memories come back
Security & data
Limitations
Upgrading
Storage layout
Config
CLI reference
MCP server
Scopes, in detail
Troubleshooting
FAQ
Project status
## Quick start
You need Node.js ≥ 22.14 (check with node -v). Then:
sh
npm install -g open-memex
open-memex init
init detects the editors you have installed (VS Code, Cursor, opencode, and
Visual Studio when your project has a solution file) and connects each one to
open-memex. Restart your editor afterwards.
See it work (30 seconds):
sh
open-memex add "This project deploys on Fridays"
Now open a new chat in your editor and ask your agent: "When does this project
deploy?" It already knows — no re-explaining. That round trip, capture once and
recall forever, is the whole product. Everything below is detail.
Optional but recommended — check everything is wired up:
sh
open-memex doctor
## Core concepts
Four ideas explain almost everything open-memex does.
1. Two scopes: project and personal.
Every memory belongs to one of two places:
project — knowledge about one codebase (decisions, constraints, lessons).
Scoped to the current repo automatically; you never set this up by hand.
personal — knowledge about you (preferences, habits) that applies in
every project. It lives only on this machine and can never be shared into a
repo.
Facts about you ("I prefer concise diffs") go to personal; everything else
defaults to the current project.
2. Capture → recall.
Memories are saved as small Markdown files, one fact each. On the first turn of
every new session, open-memex hands your agent the most relevant ones
中文文档
Every AI coding session starts from zero: you re-explain the project, the agent
rediscovers the same gotchas, and yesterday's decisions vanish when the chat
ends. open-memex gives your agents a memory that survives the session. Say
"remember: we deploy on Fridays" once, and next week Copilot, Cursor, opencode,
or Claude Code already knows — because they all read and write the same local
memory on your machine.
Free and open source (Apache-2.0). No account, no cloud, no telemetry —
everything lives on your machine, in files you can open and edit.
Local-first: memories are plain Markdown files (the source of truth) with
a rebuildable SQLite keyword index. Nothing leaves your machine unless you
explicitly share it.
One memory, every agent: wire up several editors with one command; they
share the same memory instead of keeping separate silos.
Precise synonym search: ship finds deploy, 单点登录 finds SSO —
a curated multilingual map of equivalents is indexed with every memory at
write time, so no related wording misses the right answer. Deterministic
and auditable, no embedding model required.
New here? This README takes you from install to a working memory in about a
minute. The concept guide explains the mental model in
depth once you're up and running.
## Contents
Quick start
Core concepts
Which editors, which features
Installation
Setting up your editor
What init changes on your machine
Capture: how memories get saved
Tools the agent gets
Memory types
Team workflow: sharing memories through Git
Retrieval: how memories come back
Security & data
Limitations
Upgrading
Storage layout
Config
CLI reference
MCP server
Scopes, in detail
Troubleshooting
FAQ
Project status
## Quick start
You need Node.js ≥ 22.14 (check with node -v). Then:
sh
npm install -g open-memex
open-memex init
init detects the editors you have installed (VS Code, Cursor, opencode, and
Visual Studio when your project has a solution file) and connects each one to
open-memex. Restart your editor afterwards.
See it work (30 seconds):
sh
open-memex add "This project deploys on Fridays"
Now open a new chat in your editor and ask your agent: "When does this project
deploy?" It already knows — no re-explaining. That round trip, capture once and
recall forever, is the whole product. Everything below is detail.
Optional but recommended — check everything is wired up:
sh
open-memex doctor
## Core concepts
Four ideas explain almost everything open-memex does.
1. Two scopes: project and personal.
Every memory belongs to one of two places:
project — knowledge about one codebase (decisions, constraints, lessons).
Scoped to the current repo automatically; you never set this up by hand.
personal — knowledge about you (preferences, habits) that applies in
every project. It lives only on this machine and can never be shared into a
repo.
Facts about you ("I prefer concise diffs") go to personal; everything else
defaults to the current project.
2. Capture → recall.
Memories are saved as small Markdown files, one fact each. On the first turn of
every new session, open-memex hands your agent the most relevant ones
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/stoneskin-open-memex/)
- Source
- awesome · https://github.com/stoneskin/open-memex
- Browse by field
- MCP servers
- Traction
- 6 ★
- Listed by
- 23 independent sources
- added
- today
- Security policy
- no
SECURITY.mdat the repository root (which does not mean it is unsafe)
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.