# Epitome

Shared persistent memory for coding assistants. Keeps your tech preferences and project details available across all connected agents.

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

## What it does

Epitome connects assistants to an external memory store. Instead of retyping stack details in every chat, models query a shared PostgreSQL backend. It exposes three tools: `recall`, `memorize`, and `review`. These let agents search or record details.

The backend runs on Hono, PostgreSQL 17, and `pgvector`. Each user gets a dedicated database schema. Self-hosting requires Docker Compose, while hosted accounts need an API token to communicate.

## Requirements
- Needs: Docker
- Remote server: `https://epitome.fyi/mcp`

## Install

### Claude Code (native platform)

**Platform CLI: remote server**
```bash
claude mcp add --transport http epitome https://epitome.fyi/mcp
```

### Codex

**Platform CLI: remote server**
```bash
codex mcp add epitome --url https://epitome.fyi/mcp
```

### Cursor

**Config file**
File `.cursor/mcp.json`:
```json
{
    "mcpServers": {
        "epitome": {
            "url": "https://epitome.fyi/mcp"
        }
    }
}
```

### GitHub Copilot

**Config file**
File `.vscode/mcp.json`:
```json
{
    "servers": {
        "epitome": {
            "type": "http",
            "url": "https://epitome.fyi/mcp"
        }
    }
}
```

### Gemini CLI

**Platform CLI: remote server**
```bash
gemini mcp add -t http epitome https://epitome.fyi/mcp
```

## When to use it
- persist developer preferences across separate agent sessions
- retrieve context using semantic and structured queries
- track agent read and write operations via an audit log
- share user memory between different development environments

## Example prompts
- Remember that our API responses must follow JSON:API specification.
- Recall what database engine and migration tool we chose for the backend.
- Review recent memory entries stored about our testing conventions.

## Similar
- [hypermnesia-mcp](https://affpapa.org/en/nevibecode/mcp/hypermnesia-mcp.md) — MCP server · ★ 75
- [Memory Vault](https://affpapa.org/en/nevibecode/mcp/memory-vault.md) — MCP server · ★ 65
- [memory-industry](https://affpapa.org/en/nevibecode/mcp/memory-industry.md) — MCP server · ★ 30
- [Open Brain](https://affpapa.org/en/nevibecode/mcp/open-brain.md) — MCP server · ★ 8
- [myco-brain](https://affpapa.org/en/nevibecode/mcp/myco-brain.md) — MCP server · ★ 7
- [strata](https://affpapa.org/en/nevibecode/mcp/agenerationforwordz-tech-strata.md) — MCP server · ★ 6

---
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
