Potencia tu agente
El comando propio del publicador. No es un endpoint de PlugMCP.
Host a copy with our keys and logs.
npx -y @melandlabs/[email protected]Claude Code no tiene enlace de instalación para un comando local. Copia el comando de abajo y ejecútalo en una terminal.
claude mcp add melandlabs-memory-store -- npx -y @melandlabs/memory-store@1.4.4Ejecútalo en una terminal.
{ "mcpServers": { "melandlabs-memory-store": { "command": "npx", "args": [ "-y", "@melandlabs/[email protected]" ] } }}claude_desktop_config.json
¿URL remota o un comando en tu máquina? En qué se diferencian las dos instalaciones
Ejecutar en PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
AbrirDel publicador
Your agent forgets why it made decisions. OpenContext fixes that.
The context layer for AI agents — a temporal context graph, memory API, and self-evolving loop in one dependency.
Context is the missing layer. Retrieval answers what happened. OpenContext answers how what happened became what is.
OpenContext memory storage + search SDK with HTTP and MCP server entry points.
Unlike memory libs that only retrieve, OpenContext keeps the why — temporal timelines, belief revision, and provenance.
⭐ If you find opencontext useful, please consider giving us a star on GitHub! It helps more people discover the project and motivates us to keep building. 🙏
OpenContext is the agentic context runtime that sits underneath an agentic application — and the substrate you build your own agent on top of. It is not a UI, a chat surface, or a model provider — it is the glue between the things that make an agent useful: durable memory, retrieval, context correction, multi-platform connectivity, scheduled awareness, and a deterministic loop engine, all behind one dependency.
→ Read docs/architecture.md for the full
data model, the lifecycle of a fact, and the transport surface map.
OpenContext fits teams who need to engineer their context — that is, teams whose day-to-day work runs straight into the problems OpenContext was built to solve. Each bullet spells out the pain and how OpenContext addresses it:
valid_from / valid_until, so "what did we believe last quarter?" is a real, citable query — not a guess.IntegrationRecord hides credentials, rate-limits, and reconnect logic, while platform + messageId is the natural audit trail for personal and work data.packages/loop ships exactly that separation.Third-party memory and long-context recall benchmarks (numbers current as of 2026-08):
Scores above are opencontext self-evaluations on the public datasets, produced by our own harnesses under
benchmark/. They are not Agent Memory Leaderboard (AML) results — AML evaluates against private refined datasets on its own platform. Official AML scores, once our hosted submission completes, will appear on the leaderboard card; seebenchmark/aml-local/for the submission.
There are several ways to get opencontext into your project. Pick the one that matches what you're building.
pnpm add @melandlabs/opencontext
A 30-second example of the memory API:
import { createMemoryStore, getRawMessageManager } from "@melandlabs/opencontext";
// The store defaults to SQLite at MEMORY_STORE_DB_PATH (./memory.db by
// default). Each call returns an awaitable handle.
const store = await createMemoryStore();
const messages = await getRawMessageManager();
// A message is one fact: a single piece of content attributed to a user.
// `messageId` makes the call idempotent across re-ingest.
const now = Date.now();
await messages.storeMessages([
{
messageId: "msg-1",
userId: "u-42",
content: "User prefers dark mode in all tools",
platform: "test",
botId: "bot-1",
timestamp: now,
createdAt: now,
},
]);
// Unified search fans out to memory + insights + knowledge. Sources you
// haven't wired up just emit a warning — fine for a single-backend deploy.
const hits = await store.search({
userId: "u-42",
query: "What does the user prefer?",
limit: 5,
});
// hits.count — number of results
// hits.sources — which sub-indexes were actually consulted
// hits.warnings — per-source degradation (e.g. missing embedder)
Write and query memory straight from the command line. add writes a
single raw message to the active manager with no LLM roundtrip, and
search runs a unified read across memory, insights, and knowledge.
pnpm add -g @melandlabs/opencontext # puts the `opencontext` bin on PATH
# Write a fact (auto-fills messageId, platform="cli", timestamp=now)
opencontext add --text "Rust achieves memory safety without GC"
# Write with full provenance for later consolidation
opencontext add \
--text "Discussed Q4 roadmap with the team" \
--source "meeting://2026-08-20" --kind experience \
--tag topic=roadmap --tag team=eng
# Plain hybrid search (RRF across memory + insights + knowledge)
opencontext search --query "memory safety" --k 5
# Inspect what would have been sent to the LLM, no synthesis call
opencontext search --query "what did we chat about last weekend" --context-only
# Script-friendly JSON
opencontext search --query "x" --json | jq '.results[].id'
add accepts --user (default "default"), --bot (default "default"),
--platform, --channel, --person, --source, --kind, --at,
and repeatable --tag key=value. search accepts --mode {auto|lex|sem},
--k, --threshold, repeatable --bot / --kind, --since / --until,
and --explain to surface reasoning + warnings alongside the hits.
Run opencontext <command> --help for the full flag list. See the
Getting Started tutorial
for the full flag reference and worked examples.
pnpm add -g @melandlabs/opencontext # puts the `opencontext` bin on PATH
opencontext http \
--embedding-provider local \
--memory-backend sqlite-vec \
--host 127.0.0.1 --port 7421
# Or, without a global install, via npx:
npx -y @melandlabs/opencontext http \
--embedding-provider local --memory-backend sqlite-vec
curl http://127.0.0.1:7421/health
opencontext mcp \
--embedding-provider local \
--memory-backend sqlite-vec
OpenContext is available as a DSH plugin that gives any DSH agent durable memory and retrieval-augmented context:
# Install the plugin from npm
dsh plugin --profile web add dsh-opencontext
# Confirm it's mounted
dsh --profile web --dump-config | grep dsh-opencontext
# ... should contain `id: dsh-opencontext`
# Start DSH web and verify
dsh web
# Visit http://127.0.0.1:3080/plugins and confirm dsh-opencontext shows "Enabled"
The plugin exposes 16 oc_* tools (e.g., oc_search, oc_remember, oc_memory_list) and automatically:
See plugins/dsh-opencontext/README.md for configuration options and the full tool reference.
opencontext doctor # human-readable health checks
opencontext doctor --json # CI-friendly { ok, exit, results } envelope
opencontext doctor --section memory-store
doctor is read-only and exits 0 on a healthy install. It scans nine
sections (runtime, filesystem, loop, memory-store, embedding,
policies, audit, security, integrations) and reports pass /
warn / fail for each. No auto-fix in v1.
Next: Tutorials — get started, user guide, developer guide, advanced patterns, and best practices
The examples/ workspace ships a runnable example per
capability area. Clone, install, and run:
git clone https://github.com/melandlabs/opencontext.git
cd opencontext/examples
pnpm install
pnpm test
See examples/README.md for the full walkthrough.
OpenContext is not a memory library and not a vector DB. It is a
runtime substrate — the @melandlabs/opencontext package bundles
contracts, memory-store, retrieval primitives, the loop engine, and
the agent runtime behind one dependency.
┌────────────────────────────┐
│ Host application │ ← your UI, CLI, or daemon
│ (a reference app, │
│ or your own embedder) │
└─────────────┬──────────────┘
│
┌────────────────────────┴────────────────────────┐
│ @melandlabs/opencontext │
│ contracts · memory · rag · loop · agent │
└────────────────────────┬────────────────────────┘
│
┌─────────────────────────────┴─────────────────────────────┐
│ Storage backends │
│ sqlite-vec · postgres · indexeddb · chroma · pgvector │
└─────────────────────────────┬─────────────────────────────┘
│
┌─────────────────────────────┴─────────────────────────────┐
│ Integrations mesh (gmail, slack, …) │
└───────────────────────────────────────────────────────────┘
Full data-flow diagrams, transport surfaces, and storage backends are
in docs/architecture.md.
docs/tutorials/README.md — Tutorial index and learning pathdocs/tutorials/00-getting-started.md — Get up and running in 5 minutesdocs/tutorials/01-user-guide.md — Understand the four verbs and temporal memorydocs/tutorials/02-developer-guide.md — Integrate OpenContext into your appdocs/tutorials/03-advanced-usage.md — Production patterns and advanced featuresdocs/tutorials/04-best-practices.md — Tips and common pitfallsdocs/tutorials/use-cases/README.md — Real-world use cases: personal assistant, support agent, research trackerdocs/architecture.md — data model, lifecycle, data plane and control planedocs/philosophy.md — why this shapeREADME.md — API surface, examples, migration notesSee CONTRIBUTING.md.
Apache-2.0. © 2026 Meland Labs.
OpenContext memory storage + search SDK with HTTP and MCP server entry points.
{ "mcpServers": { "melandlabs-memory-store": { "command": "npx", "args": [ "-y", "@melandlabs/[email protected]" ] } }}Herramientas
Aún no hay lista de herramientas. Los servidores remotos la reciben tras la primera comprobación de estado.
Preguntas frecuentes
Copia en esta página la configuración stdio para Cursor, Claude Desktop, Claude Code o VS Code. Usa la instalación del publicador, no un proxy de PlugMCP.
Este registro no indica ninguna variable de entorno obligatoria.
@melandlabs/memory Store se ejecuta localmente por stdio.
Última comprobación: 2026-11-15. OpenContext memory storage + search SDK with HTTP and MCP server entry points.