# Mneme Memory

Saves developer context and habits across sessions using a local SQLite store. It keeps track of project rules, conventions, and past decisions so the agent does not ask twice.

- MCP server · `type=mcp` · Claude Code, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Cline, Zed, Gemini CLI · ★ 177
- Author: slow-stack
- License: MIT · policy=link-only · description only; the file stays with the author
- Source: https://github.com/slow-stack/mneme
- Updated: 2026-10-24
- HTML: https://affpapa.org/en/nevibecode/mcp/mneme-memory

## What it does

Mneme Memory brings persistent memory to coding assistants so you do not repeat project requirements in every new session. It stores all facts locally in an SQLite database. It keeps memory files in Markdown format. You can inspect or modify these text files by hand anytime.

Background workers consolidate related notes and compress stale records over time. When new statements contradict earlier facts, the server pauses the update instead of guessing. It holds conflicts in a queue for user review. You can also restrict context by workspace and project path. This boundary stops unrelated details from leaking across repositories.

Running the server requires Node.js 22 or newer on your machine. Semantic search functions without external API keys if you set the provider to local embeddings or BM25 text retrieval.

## Requirements
- Needs: Node.js (commands run via npx)

## Install

### Claude Code (native platform)

**Platform CLI**
```bash
claude mcp add mneme-memory -- npx -y mneme-memory
```

### Codex

**Platform CLI**
```bash
codex mcp add mneme-memory -- npx -y mneme-memory
```

### Cursor

**Config file**
File `.cursor/mcp.json`:
```json
{
    "mcpServers": {
        "mneme-memory": {
            "command": "npx",
            "args": [
                "-y",
                "mneme-memory"
            ]
        }
    }
}
```

### GitHub Copilot

**Config file**
File `.vscode/mcp.json`:
```json
{
    "servers": {
        "mneme-memory": {
            "type": "stdio",
            "command": "npx",
            "args": [
                "-y",
                "mneme-memory"
            ]
        }
    }
}
```

### Gemini CLI

**Platform CLI**
```bash
gemini mcp add mneme-memory npx -y mneme-memory
```

## When to use it
- maintain coding conventions across separate chat sessions
- isolate context between different projects and agents
- hold conflicting facts in a queue for manual resolution
- retrieve architectural decisions offline via local search

## Example prompts
- Remember that we use four spaces for indentation and TypeScript for all frontend components.
- Search long-term memory for the database we picked for the billing service last week.
- Check project memory and list our current conventions for writing tests.

## Similar
- [REA](https://affpapa.org/en/nevibecode/mcp/rea.md) — MCP server · ★ 386989
- [GitHub](https://affpapa.org/en/nevibecode/mcp/github.md) — MCP server · ★ 33918
- [Netdata](https://affpapa.org/en/nevibecode/mcp/netdata.md) — MCP server · ★ 81115
- [browser-use](https://affpapa.org/en/nevibecode/mcp/browser-use.md) — MCP server · ★ 119160
- [Codebase Memory](https://affpapa.org/en/nevibecode/mcp/codebase-memory.md) — MCP server · ★ 47392
- [mcp-server](https://affpapa.org/en/nevibecode/mcp/mcp-server.md) — MCP server · ★ 43872

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md