原型 · 预览版：收录官方注册中心里的全部服务器，每 30 分钟同步一次。评价和账户功能将在后续阶段推出。
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚
新手模式 开
配色跟随系统浅色深色
语言ไทยEnglish中文日本語한국어EspañolDeutsch
☰ 菜单设置
新手模式 开
配色跟随系统浅色深色
语言ไทยEnglish中文日本語한국어EspañolDeutsch

open-memex

作者：stoneskin版本 0.9.0i★ –i在你的电脑上运行
注册名称io.github.stoneskin/open-memex

安装

概览

作者提供的说明（英文原文）

Local-first memory for AI coding agents — Markdown + SQLite FTS5, shared across editors via MCP.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

  • 连接方式: 在你的电脑上运行
  • 传输方式: stdio
  • 分类: 开发者工具

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

  • 基础检查：1 项中通过 1 项
  • 在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
  • 注册中心没有列出需要填写的密钥。

你需要

  • npm已安装 Node.js（用于 npx 命令）

你用的是哪个应用？

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "open-memex": {
      "command": "npx",
      "args": [
        "-y",
        "open-memex",
        "mcp"
      ]
    }
  }
}

在终端中运行这条命令

claude mcp add open-memex -- npx -y open-memex mcp

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "open-memex": {
      "command": "npx",
      "args": [
        "-y",
        "open-memex",
        "mcp"
      ]
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "open-memex": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "open-memex",
        "mcp"
      ]
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 stoneskin 验证，该账户拥有此仓库

  • … 尚未检查

    仍在维护

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    有许可证

    我们还没有从 GitHub 读取这个仓库

  • – 不适用

    端点有响应

    它在你的电脑上运行，没有互联网端点

  • – 不适用

    使用 OAuth 登录

    在你的电脑上运行，改用本地设置

  • … 尚未检查

    工具描述中没有隐藏指令

    它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“开发者工具”中的其他服务器比较i

  • 星标数多于此分类中其他 5135 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 5135 个服务器的 91% 更新
  • 基础检查结果等于或优于此分类中其他 5135 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

open-memex 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

注册中心没有列出必需的密钥，不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.9.0）于前天进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。

有什么可以替代它？

同一分类中有：GitHub, Desktop Commander, Cloudflare MCP

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：↓ 每周下载量i★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

GitHub

Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.

作者：github广泛使用★ 3.4万5天前更新

电脑或云端
安装

Desktop Commander

MCP server for terminal commands, file operations, and process management

作者：wonderwhy-er广泛使用↓ 71万/周★ 1万17天前更新

在你的电脑上运行
安装

Cloudflare MCP

Cloudflare MCP servers

作者：cloudflare正在增长★ 444614个月前更新

在云端运行✓ mcp.cloudflare.com
安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

open-memex

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.
  • A map, not just search: a derived knowledge graph connects your project memories — supersedes chains, shared tags, explicit mentions — and injects a compiled outline at session start, so the agent sees what's in memory without searching. Structural edges only, no LLM.

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
  • How it compares
  • 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
  • Session working state
  • Knowledge graph
  • MCP server
  • Scopes, in detail
  • Troubleshooting
  • FAQ
  • Project status

Quick start

You need Node.js ≥ 22.14 (check with node -v). Then:

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):

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:

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 automatically, so it starts the session already knowing them. The agent can also search the full memory on demand. You never have to "load" anything yourself.

3. Your files, your rules. The Markdown files are the source of truth — open them, edit them, delete them, grep them. The SQLite index next to them is just a search accelerator and rebuilds from the files at any time (open-memex reindex). Team sharing, when you want it, goes through the same review flow as code: nothing is shared automatically (see Team workflow).

4. Knowledge stays current. Facts change: decisions get reversed, tools get replaced, yesterday's gotcha gets fixed. open-memex doesn't let the old version quietly linger — memory_supersede replaces a memory with its newer version and keeps the chain, so retrieval serves the current fact while the history stays auditable. Merely stale memories can be deprecated, and open-memex audit reports duplicates, stale entries, and broken chains. Pruning is a feature, not housekeeping: shared memory rots without it.

Which editors, which features

open-memex talks to editors two ways: a native opencode plugin, and a standard MCP server that any MCP-capable editor can use. (MCP — Model Context Protocol — is the open standard editors use to give agents extra tools; open-memex appears in your editor as a set of memory_* tools.) What you get depends on which path an editor uses:

EditorSetupToolsSession-start recallKeyword auto-capture
opencode (native plugin, recommended)open-memex init --client opencode --global6 core toolsBuilt in — first turn of every sessionYes — remember …, 记住…
VS Code (Copilot)open-memex init --client vscodeAll 12 via MCPVia MCP guidance*No — the agent saves when you ask
Cursoropen-memex init --client cursorAll 12 via MCPVia MCP guidance*No — the agent saves when you ask
Claude Codeclaude mcp add open-memex -- open-memex mcpAll 12 via MCPVia MCP guidance*No — the agent saves when you ask
Visual Studio 2022 17.14+ / 2026open-memex init --client visualstudioAll 12 via MCPVia MCP guidance*No — the agent saves when you ask
Codex and other MCP clientsopen-memex mcp --print-configAll 12 via MCPVia MCP guidance*No — the agent saves when you ask

\* MCP has no hard session-start hook, so open-memex sends the agent guidance in the MCP handshake (including how many drafts are waiting) and init writes the fuller version into the editor's instruction files. In practice agents follow it; the opencode plugin is the only path with true built-in first-turn injection. The Tools section lists the 6 core tools and the 6 extra workflow tools, so the "6 vs 12" split is explicit.

All editors on the same machine read and write the same memory — a constraint captured in VS Code is respected in opencode; a lesson learned in Cursor shows up in Claude Code. (Different machines do not sync automatically; see the FAQ.)

init also installs an Agent Skill (a short instruction file that teaches skill-aware agents to use the CLI) for VS Code and Cursor, and for opencode in per-project MCP mode. With the opencode native plugin wired, no skill is installed there — the plugin already provides the memory tools, and a second instruction set only made agents chatty.

How it compares

open-memexInstruction files (CLAUDE.md, AGENTS.md, …)Cloud memory servicesChat history
Where it livesYour machine + your reposIn the repoVendor serversGone when the chat ends
Who maintains itCaptured as you work; you reviewYou write and update by handThe service—
When facts changeSuperseded, not silently stale — retrieval serves the current version, chain preservedYou hand-edit; stale copies lingerVaries; often silently stale—
Works across AI toolsYes — any MCP client (same machine)One file per tool conventionPer-integrationNo
Review before sharingYes — outbox + pull requestYes — it's just filesVariesNo
Human-readablePlain Markdown filesYesDashboard / APINo

Instruction files are great for a handful of standing rules — keep using them (open-memex can even draft one from your memories; see distill-agents below). open-memex covers the growing pile of decisions, lessons, and preferences that no one remembers to write down.

Installation

Requirements
  • Node.js ≥ 22.14 (open-memex doctor verifies this for you). The floor is the SQLite driver's: better-sqlite3 13 is built against Node-API 10, which Node gained in 22.14.0 — older Node segfaults on the first database open.
Install the CLI
npm install -g open-memex

That's the stable release. Installing the package may print a reminder to run open-memex init — the editor wiring is a separate step (see Setting up your editor), so don't worry if you don't see the reminder; just run init next.

Two alternatives:

  • No install — run via npx: npx -y open-memex runs any command without installing (e.g. npx -y open-memex init --client vscode). Slower to start, nothing to uninstall.
  • Alpha builds (newest features, rougher edges, for testers): npm install -g open-memex@alpha. Check what's published with npm view open-memex version (stable) and npm view open-memex@alpha version (alpha).

If open-memex isn't found after installing, your PATH needs attention — see Troubleshooting.

From source (for contributors)
git clone -b main https://github.com/stoneskin/open-memex.git

cd open-memex npm install node --experimental-strip-types src/cli.ts

Setting up your editor

Run init from your project root (the top folder of the repo you're working in) so the project scope resolves to that repo:

open-memex init --yes

…or without installing the package first:

npx -y open-memex init --yes

--yes accepts the recommended defaults for everything init asks about (editors to wire, auto-capture, first-turn recall). Leave it off if you want to answer each question. With no --client, init detects your installed editors and wires them all — one init covers every project. Prefer a single editor? Pass --client:

VS Code (Copilot):

open-memex init --client vscode

Writes the MCP server entry; reload the window afterwards and confirm the open-memex server is started in Copilot Chat's MCP panel. By default this writes a project-level .vscode/mcp.json (an interactive run asks which level you want); add --global for VS Code's *user-level* config inst

只显示了开头部分；其余内容请在仓库中阅读

问 PopNx