The portable identity layer that gives every AI agent a shared, persistent memory of you.
Epitome MCP server exists for a simple reason — assistants are far more useful when they can act on Epitome directly instead of describing what you should do. The portable identity layer that gives every AI agent a shared, persistent memory of you.
Once Epitome is connected, these are the calls the assistant has available:
Self — hosters** who want full data ownership — no cloud requiredPer — user PostgreSQL schema isolation** — not row-level security, full schema separationAppend — only audit log** — every access is recordedGDPR-ready — export or delete all your data at any timeSelf-hostable — The Self-hostable tool exposed by this serverComponent — TechnologyRuntime — Node.js 22 LTSAPI — HonoDatabase — PostgreSQL 17 + pgvectorMCP — @modelcontextprotocol/sdkFrontend — React 19 + Tailwind CSS 4 + shadcn/uiValidation — ZodYou will need one environment variable: YOUR_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
Plenty of database access servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Epitome's toolset — Self, Per, Append and 10 more — is a fair guide to whether it matches your workflow. It is maintained by gunning4it; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Self | hosters** who want full data ownership — no cloud required |
| Per | user PostgreSQL schema isolation** — not row-level security, full schema separation |
| Append | only audit log** — every access is recorded |
| GDPR-ready | export or delete all your data at any time |
| Self-hostable | The Self-hostable tool exposed by this server. |
| Component | Technology |
| Runtime | Node.js 22 LTS |
| API | Hono |
| Database | PostgreSQL 17 + pgvector |
| MCP | @modelcontextprotocol/sdk |
| Frontend | React 19 + Tailwind CSS 4 + shadcn/ui |
| Validation | Zod |
| Testing | Vitest |
| Variable | Description | Required |
|---|---|---|
| YOUR_API_KEY | Credential the server authenticates with. | Yes |
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.