Context7
Up-to-date docs for AI agents
Descripción del creador (original en inglés)
Persistent cross-project memory for Cursor and Claude Code using local semantic search.
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
Elige la app de IA que usas y copia la configuración.
Necesitas
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Abre Claude Desktop → Settings → Developer → Edit Config y pega esto en claude_desktop_config.json
{
"mcpServers": {
"longmem": {
"command": "uvx",
"args": [
"longmem"
]
}
}
}Ejecuta esto en tu terminal
claude mcp add longmem -- uvx longmemPégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"longmem": {
"command": "uvx",
"args": [
"longmem"
]
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Pégalo en .vscode/mcp.json de tu proyecto
{
"servers": {
"longmem": {
"type": "stdio",
"command": "uvx",
"args": [
"longmem"
]
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Este se ejecuta en tu computadora, y ChatGPT solo puede conectarse a servidores en internet. Elige otra app.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 6 nov 2026
El nombre en el registro se verificó con la cuenta de GitHub marerem, dueña del repo
Todavía no hemos leído este repo en GitHub
Todavía no hemos leído este repo en GitHub
Este se ejecuta en tu computadora; no hay endpoint en internet
Se ejecuta en tu computadora y usa ajustes locales en su lugar
Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
El registro no indica ninguna clave obligatoria, aunque algunos servidores te piden iniciar sesión la primera vez que los usas.
Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).
El repo de GitHub cambió por última vez –, y la última versión (0.2.1) llegó al registro hace 7 meses.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas Python (uv) en tu computadora.
En la misma categoría: Context7, Codebase Memory, Exa
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
Up-to-date docs for AI agents
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
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
| longmem | others | |
|---|---|---|
| Cost | Free — local Ollama embeddings | Requires API calls per session |
| Privacy | Nothing leaves your machine | Sends observations to external APIs |
| Process | Starts on demand, no daemon | Background worker + open port required |
| IDE support | Cursor + Claude Code | Primarily one IDE |
| Search | Hybrid: semantic + keyword (FTS5) | Vector-only or keyword-only |
| Teams | Export / import / shared DB path / S3 | Single-user |
| License | MIT | AGPL / proprietary |
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.
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.
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
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.
| Command | What it does |
|---|---|
longmem init | One-time setup: Ollama check, model pull, writes IDE config |
longmem install | Copy rules into the current project |
longmem status | Config, 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 review | Manually save a solution when the AI forgot |
longmem with no arguments starts the MCP server (used by your IDE).
Config lives at ~/.longmem/config.toml. All fields are optional — defaults work with a local Ollama instance.
embedder = "openai"
openai_model = "text-embedding-3-small" openai_api_key = "sk-..." # or set OPENAI_API_KEY
Install the extra: pip install 'longmem[openai]'
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"
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.
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:
| Layer | Scope | How to save |
|---|---|---|
| 1. General pattern | Universal — any team | always include in solution text |
| 2. Team-wide fact | Your whole stack | project="shared" |
| 3. Project detail | One repo only | project=" " + enrich_solution |
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)
The server exposes 11 tools. The two you interact with most:
keyword_match flag when the hit came from exact text rather than vector similarity.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.
Categories pre-filter before vector search — keeps retrieval fast at any scale.
| Category | Use for |
|---|---|
ci_cd | GitHub Actions, Jenkins, GitLab CI, build failures |
containers | Docker, Kubernetes, Helm, OOM kills |
infrastructure | Terraform, Pulumi, CDK, IaC drift |
cloud | AWS/GCP/Azure SDK, IAM, quota errors |
networking | DNS, TLS, load balancers, timeouts, proxies |
observability | Logging, metrics, tracing, Prometheus, Grafana |
auth_security | OAuth, JWT, RBAC, secrets, CVEs |
data_pipeline | Airflow, Prefect, Dagster, ETL, data quality |
ml_training | GPU/CUDA, distributed training, OOM |
model_serving | vLLM, Triton, inference latency, batching |
experiment_tracking | MLflow, W&B, DVC, reproducibility |
llm_rag | Chunking, embedding, retrieval, reranking |
llm_api | Rate limits, token cost, prompt engineering |
vector_db | Pinecone, Weaviate, Qdrant, LanceDB |
agents | LangChain, LlamaIndex, tool-calling, agent memory |
database | SQL/NoSQL, migrations, slow queries |
api | REST, GraphQL, gRPC, versioning |
async_concurrency | Race conditions, event loops, deadlocks |
dependencies | Version conflicts, packaging, lock files |
performance | Profiling, memory leaks, caching |
testing | Flaky tests, mocks, integration vs unit |
architecture | Design patterns, service boundaries, refactoring |
other | When nothing above fits |
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:
Ways to contribute without code:
MIT — see LICENSE.
mcp-name: io.github.marerem/longmem