Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Longmem

by mareremversion 0.2.1i★ –iRuns on your computer
Registry nameio.github.marerem/longmem

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

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

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

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).
  • The registry lists no key to fill in.

You need

  • PyPIPython’s uv installed (for the uvx command)

Which app do you use?

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": {
    "longmem": {
      "command": "uvx",
      "args": [
        "longmem"
      ]
    }
  }
}

Run this in your terminal

claude mcp add longmem -- uvx longmem

Open in Cursor

Or copy the settings yourself

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

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

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": {
    "longmem": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "longmem"
      ]
    }
  }
}

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.

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 6, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account marerem, 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 7233 servers in this category
  • Published to the registry more recently than 9% of the other 7233 servers in this category
  • Basic checks equal to or better than 100% of the other 7233 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 Longmem 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?

The registry does not list a required key, though some servers ask you to sign in on first use.

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.2.1) reached the registry 7 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) 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:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Context7

by upstash

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

Computer or cloud★ 64,224MITUpdated 3 days ago
Install

Codebase Memory

by DeusData

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

Runs on your computer★ 48,148MITUpdated 20 days ago
Install

Exa

by exa-labs

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

Runs in the cloud★ 5,213MITUpdated 44 days ago
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.

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

Ask PopNx