switch to 3ngram ·hosted · self-hosted · explicit capture

keep the tools you already use. add one shared memory layer behind them.

Connect over MCP, choose what to remember, then retrieve it explicitly from another session or client. 3ngram does not passively import your history.

switch ·explicit capture, not bulk import

three starting points.

path 01 — hostedmanaged service

connect the AI client you already use over MCP.

Sign up, add https://mcp.3ngram.ai/mcp to Claude, ChatGPT, Cursor, Codex, or another compatible client, and complete the browser authorization flow. The same account and typed memory are then available to every client you connect.

managed MCP endpoint · browser OAuthget started free →
01create your account and open the client setup guide.02add the MCP endpoint and approve memory read/write access.03ask the client to remember one typed decision or commitment.04open another session and ask it to search that memory.
path 02 — self-hostedApache-2.0 backend

run the memory backend on infrastructure you control.

The public repository includes the MCP server, REST API, SDK, CLI, worker, migrations, and a Docker Compose setup for Postgres with pgvector and Redis. The managed dashboard and billing system are separate proprietary services and are not required to run the backend.

source available · Docker Compose · no phone-homeread the self-host guide ↗
01clone the public repository and copy .env.selfhost.example.02set the required secrets and embedding-provider configuration.03run the migration service, then start the stack.04connect an OAuth-capable client to your server's /mcp endpoint.
path 03 — existing contextselect what matters

leave your existing history where it is. carry forward the useful state.

Bulk upload of Claude or ChatGPT exports is not a launch feature. Instead, connect a client and explicitly save the decisions, commitments, blockers, facts, and preferences that should survive. The REST API and TypeScript SDK are available for programmatic writes when you already have structured records.

no passive import · explicit MCP or REST writesconnect a client →
01choose one current project, scope, or decision thread.02ask your client to debrief the specific records worth keeping.03review what it proposes, then invoke remember for each record.04use briefing or search when you want it back.
switch ·defaults we think are sane

safety rails on day one.

capture is explicit.
3ngram does not scrape conversations or save a session unless you or the client invokes a write operation.
safe
source connectors and outbound agents are not part of v1.
There is no automatic repository, document, calendar, email, or chat ingestion, and 3ngram does not send messages or open pull requests.
safe
nothing is mixed with other tenants' data in queries.
row-level security on every query, enforced at the database layer.
safe
corrections preserve the history.
Revise and resolve operations append events and superseding records; they do not silently replace memory text in place.
safe

start with one memory worth keeping.

prefer the full walkthrough? read the quickstart ↗ · connecting tools ↗

get started free ↵