epitome

The Problem

Every AI conversation starts from zero. You repeat yourself to every agent — your name, your preferences, your allergies, your tech stack. Chat history is siloed per app. There's no portable memory layer.

Epitome fixes this. One database that every AI agent shares, so they all remember you.

Related MCP server: Memsolus MCP Server

Quickstart

Hosted (fastest)

1. Sign up at epitome.fyi

2. Go to Settings → API Keys and copy your MCP URL

3. Connect an AI agent — done

Self-Hosted

git clone https://github.com/gunning4it/epitome.git
cd epitome
cp .env.example .env    # edit with your credentials
docker compose up -d

Open localhost:5173 and sign in with Google or GitHub OAuth.

Connect an AI Agent

Get your API key from Settings → API Keys in the dashboard (hosted or self-hosted).

Claude Desktop

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "epitome": {
      "url": "https://epitome.fyi/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Claude Code

claude mcp add --transport http --header "Authorization: Bearer YOUR_API_KEY" epitome https://epitome.fyi/mcp

Self-Hosted

For self-hosted, replace https://epitome.fyi with http://localhost:3000.

Epitome exposes 3 MCP tools — recall, memorize, and review. See the full tool reference.

Who This Is For

• AI developers building agents that need persistent user memory

• Power users who want every AI to remember them across platforms

• Self-hosters who want full data ownership — no cloud required

Use Cases

• Your meal-tracking agent remembers your allergies

• Your coding assistant knows your stack, your patterns, your team

• Your calendar agent knows your family, your priorities, your routines

• Every new AI tool you try already knows you on day one

Why Epitome?

The Five Layers

Architecture

AI Agent ──→ MCP (Streamable HTTP) ──→ Hono API ──→ PostgreSQL
                                         │
                                    per-user schema
                                      isolation

Each user gets their own PostgreSQL schema (user_{id}) — not row-level security, full schema-level isolation. Cross-schema access is impossible at the SQL level.

See EPITOME_TECH_SPEC.md for the full architecture.

Security & Privacy

• You own your data — self-host or use the hosted service

• Per-user PostgreSQL schema isolation — not row-level security, full schema separation

• Per-agent consent rules — you control what each agent can read and write

• Append-only audit log — every access is recorded

• GDPR-ready — export or delete all your data at any time

Tech Stack

Documentation

• Quick Start — Get running in minutes

• JavaScript SDK — Build with @epitomefyi/sdk

• npm Package — Install and version history

• AI SDK Tools — searchMemory, saveMemory, getUserContext for tool-calling

• API Reference — REST endpoint documentation

• MCP Tools — All 3 MCP tools explained

• Architecture — Full technical specification

• Data Model — Every table, column, and constraint

• Self-Hosting Guide — Docker Compose deployment

• Security — Isolation, consent, and audit

Contributing

Contributions are welcome! See CONTRIBUTING.md for guidelines.

git clone https://github.com/gunning4it/epitome.git
cd epitome && cp .env.example .env
docker compose up -d

Then open a PR — we're happy to help with your first contribution.

License

MIT