原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。评价和账户功能将在后续阶段推出。
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

Longmem

作者:marerem版本 0.2.1i★ –i在你的电脑上运行
注册名称io.github.marerem/longmem

安装

概览

作者提供的说明(英文原文)

Persistent cross-project memory for Cursor and Claude Code using local semantic search.

PopNx MCP 的三大支柱

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

它能帮你做什么

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

  • 连接方式: 在你的电脑上运行
  • 传输方式: stdio
  • 分类: 搜索与 AI 记忆

安装

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

安装之前

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

你需要

  • PyPI已安装 Python 的 uv(用于 uvx 命令)

你用的是哪个应用?

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

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

{
  "mcpServers": {
    "longmem": {
      "command": "uvx",
      "args": [
        "longmem"
      ]
    }
  }
}

在终端中运行这条命令

claude mcp add longmem -- uvx longmem

在 Cursor 中打开

或者自己复制设置

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

{
  "mcpServers": {
    "longmem": {
      "command": "uvx",
      "args": [
        "longmem"
      ]
    }
  }
}

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

在 VS Code 中打开

或者自己复制设置

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

{
  "servers": {
    "longmem": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "longmem"
      ]
    }
  }
}

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

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

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

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

它能做什么

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

基础检查i

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

  • ✓ 通过

    作者与仓库一致

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

  • … 尚未检查

    仍在维护

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

  • … 尚未检查

    有许可证

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

  • – 不适用

    端点有响应

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

  • – 不适用

    使用 OAuth 登录

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

  • … 尚未检查

    工具描述中没有隐藏指令

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

与“搜索与 AI 记忆”中的其他服务器比较i

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

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

常见问题

Longmem 安全吗?

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

它需要哪些密钥或代码?

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

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

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

它还在维护吗?

GitHub 仓库最后更新于–,最新版本(0.2.1)于7个月前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。

有什么可以替代它?

同一分类中有:Context7, Codebase Memory, Exa

替代选择

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

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

Context7

作者:upstash

Up-to-date docs for AI agents

电脑或云端★ 64,224MIT今天更新
安装

Codebase Memory

作者:DeusData

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

在你的电脑上运行★ 48,148MIT20天前更新
安装

Exa

作者:exa-labs

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

在云端运行★ 5,213MIT上个月更新
安装

作者的 README

打开 README

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

Cross-project memory for AI coding assistants. Stop solving the same problems twice.


Your AI solves the same bug in a different project six months later. Writes the same boilerplate. Explains the same pattern. You already knew the answer.

longmem gives your AI a persistent memory that works across every project and every session. Before reasoning from scratch, it searches what you've already solved. After something works, it saves it. The longer you use it, the less you repeat yourself.

You describe a problem

│ ▼ search_similar() ┌─────────────────────────────────────────────────────┐ │ 1. pre-filter by category (ci_cd / auth / db / …) │ │ 2. semantic search (Ollama or OpenAI embeddings) │ │ 3. keyword search (SQLite FTS5 exact match) │ │ 4. merge + rank results │ └─────────────────────────────────────────────────────┘ │ │ score ≥ 85% score < 85% │ │ ▼ ▼ cached solution AI reasons from scratch

  • edge cases │
  • team knowledge "it works" (any project) │ ▼ confirm_solution() saved once — surfaces from every future project

Why longmem

longmemothers
CostFree — local Ollama embeddingsRequires API calls per session
PrivacyNothing leaves your machineSends observations to external APIs
ProcessStarts on demand, no daemonBackground worker + open port required
IDE supportCursor + Claude CodePrimarily one IDE
SearchHybrid: semantic + keyword (FTS5)Vector-only or keyword-only
TeamsExport / import / shared DB path / S3Single-user
LicenseMITAGPL / proprietary

Quickstart

1. Install

pipx install longmem

2. Setup — checks Ollama, pulls the embedding model, writes your IDE config

longmem init

3. Activate in each project — copies the rules file that tells the AI how to use memory

cd your-project

longmem install

4. Restart your IDE. Memory tools are now active on every chat.

Need Ollama? Install from ollama.com, then ollama pull nomic-embed-text. Or use OpenAI — see Configuration.


How it works

longmem is an MCP server. Your IDE starts it on demand. Two rules drive the workflow:

Rule 1 — search first. Before the AI reasons about any bug or question, it calls search_similar. If a match is found (cosine similarity ≥ 85%), the cached solution is returned with any edge-case notes. Below the threshold, the AI solves normally.

Rule 2 — save on success. When you confirm something works, the AI calls confirm_solution. One parameter — just the solution text. Problem metadata is auto-filled from the earlier search.

The rules file (longmem.mdc for Cursor, CLAUDE.md for Claude Code) wires this up automatically. No manual prompting.

AI forgot to save? Run longmem review — an interactive CLI to save any solution in 30 seconds.

Cold start — getting value from day one

longmem is most useful once it has entries. The fastest way to seed it:

Option 1 — review as you go. After every solved problem this week, run longmem review and describe what you fixed. Ten entries is enough to feel the difference.

Option 2 — team import. If a teammate already has entries, they export and you import:

# teammate

longmem export team_knowledge.json

you

longmem import team_knowledge.json

Option 3 — shared DB. Set db_path (or db_uri for S3/cloud) to the same location for the whole team. Every save is instantly available to everyone.


CLI

CommandWhat it does
longmem initOne-time setup: Ollama check, model pull, writes IDE config
longmem installCopy rules into the current project
longmem statusConfig, Ollama reachability, entry count, DB size
longmem export [file]Dump all entries to JSON — backup or share
longmem import Load a JSON export — onboard teammates or migrate machines
longmem reviewManually save a solution when the AI forgot

longmem with no arguments starts the MCP server (used by your IDE).


Configuration

Config lives at ~/.longmem/config.toml. All fields are optional — defaults work with a local Ollama instance.

Switch to OpenAI embeddings
embedder       = "openai"

openai_model = "text-embedding-3-small" openai_api_key = "sk-..." # or set OPENAI_API_KEY

Install the extra: pip install 'longmem[openai]'

Team shared database

Point every team member's config at the same path:

# NFS / shared drive

db_path = "/mnt/shared/longmem/db"

Or use cloud storage:

# S3 (uses AWS env vars)

db_uri = "s3://my-bucket/longmem"

LanceDB Cloud

db_uri = "db://my-org/my-db" lancedb_api_key = "ldb_..." # or set LANCEDB_API_KEY

No shared mount? Use longmem export / longmem import to distribute a snapshot.

Team knowledge base

Save facts that are true across your whole stack under project="shared" so they surface from any repo:

save_solution(

problem="why oauth2-proxy uses port 4181 not default 4180", solution="General: 4180 is the oauth2-proxy default. 4181 means something else already occupies 4180.\n\nThis team's setup: Sinfonia always runs on 4180. Every other project uses 4181+ by convention.", project="shared", category="networking", tags=["oauth2-proxy", "ports", "nginx"] )

search_similar searches all projects — a shared entry surfaces automatically from any repo without needing search_by_project.

Three-layer solution format — write solutions so they work for anyone who finds them:

LayerScopeHow to save
1. General patternUniversal — any teamalways include in solution text
2. Team-wide factYour whole stackproject="shared"
3. Project detailOne repo onlyproject=" " + enrich_solution
Tuning
similarity_threshold = 0.85   # minimum score to surface a cached result (default 0.85)

duplicate_threshold = 0.95 # minimum score to block a save as a near-duplicate (default 0.95)


MCP tools

The server exposes 11 tools. The two you interact with most:

  • `search_similar` — semantic + keyword hybrid search. Returns ranked matches with similarity scores, edge cases, and a keyword_match flag when the hit came from exact text rather than vector similarity.
  • `confirm_solution` — saves a solution with one parameter. Problem metadata auto-filled from the preceding search.

Full list: save_solution, correct_solution, enrich_solution, add_edge_case, search_by_project, delete_solution, rebuild_index, list_recent, stats.

Call rebuild_index once you reach 256+ entries to compact the database and build the ANN index for faster search.


Category reference

Categories pre-filter before vector search — keeps retrieval fast at any scale.

CategoryUse for
ci_cdGitHub Actions, Jenkins, GitLab CI, build failures
containersDocker, Kubernetes, Helm, OOM kills
infrastructureTerraform, Pulumi, CDK, IaC drift
cloudAWS/GCP/Azure SDK, IAM, quota errors
networkingDNS, TLS, load balancers, timeouts, proxies
observabilityLogging, metrics, tracing, Prometheus, Grafana
auth_securityOAuth, JWT, RBAC, secrets, CVEs
data_pipelineAirflow, Prefect, Dagster, ETL, data quality
ml_trainingGPU/CUDA, distributed training, OOM
model_servingvLLM, Triton, inference latency, batching
experiment_trackingMLflow, W&B, DVC, reproducibility
llm_ragChunking, embedding, retrieval, reranking
llm_apiRate limits, token cost, prompt engineering
vector_dbPinecone, Weaviate, Qdrant, LanceDB
agentsLangChain, LlamaIndex, tool-calling, agent memory
databaseSQL/NoSQL, migrations, slow queries
apiREST, GraphQL, gRPC, versioning
async_concurrencyRace conditions, event loops, deadlocks
dependenciesVersion conflicts, packaging, lock files
performanceProfiling, memory leaks, caching
testingFlaky tests, mocks, integration vs unit
architectureDesign patterns, service boundaries, refactoring
otherWhen nothing above fits

Contributing

Contributions are very welcome — this project grows with the community that uses it.

Whether it's a bug fix, a new feature, better docs, or just sharing your use case — all of it helps. If you're unsure whether an idea fits, open an issue first and we'll figure it out together.

Getting started:

git clone https://github.com/marerem/longmem

cd longmem uv sync --group dev uv run pytest

Good first contributions:

  • New category suggestions
  • Edge cases you hit in real projects
  • IDE integrations (JetBrains, VS Code, Neovim, etc.)
  • Better error messages
  • Seed datasets — export your own entries and share them as a starter pack

Ways to contribute without code:

  • Star the repo if you find it useful
  • Share it with your team
  • Open an issue if something is confusing — unclear UX is a bug

License

MIT — see LICENSE.

mcp-name: io.github.marerem/longmem

问 PopNx