Persistent cognitive memory for AI coding tools. Your AI coding tool has amnesia. memeX fixes it. Local-first, MCP-native, ships with curated skills any AI can install and validate against. Also acts as an MCP gateway — one connection, two tool families: memeX’s native memory tools plus every upstream MCP server you wire in.
In one diagram
┌─────────────────────────────────────┐
│ memeX core engine │
│ storage + retrieval + lifecycle │
│ + working set + ML — protocol-blind │
└─────────────────────────────────────┘
▲ ▲ ▲
│ │ │
┌──────────┴──────┐ ┌─┴────┐ ┌───┴────┐
│ MCP frontend │ │ HTTP │ │ CLI │
│ (stdio) │ │ API │ │ │
└─────────────────┘ └──────┘ └────────┘In three sentences
memeX is a local daemon giving Claude Code, Cursor, Windsurf, Cline, and any HTTP-capable AI tool a shared persistent memory — graph-structured, budget-bounded, provenance-stamped. It also ships skills: installable validation bundles (security, money, concurrency, crypto, SQL, untrusted input) the AI must self-attest against before generating sensitive code. Every action is logged, every confidence decays over time, every retrieval is bounded by tokens — modeled jointly on RAM hardware and human memory.
Where to go next
Quickstart
60 seconds from install to first recall.
Concepts
The RAM ↔ human-memory ↔ memeX mapping and the axiomatic derivation of the architecture.
Skills
What skills are, the three builtin bundles, how to author your own.
Editor recipes
Wire memeX into Claude Code, Cursor, Windsurf, Cline, or any HTTP client.
HTTP API reference
Every endpoint, auth model, example requests.
Download
pipx, uv, Docker, or source.
Status
v1.0 — generally available. Apache 2.0 licensed, no telemetry, runs entirely on your machine. File issues on github.com/queflyhq/memex.