Persistent memory
for Claude.
Claude forgets everything between sessions. CMK fixes that. Your preferences, decisions, and context persist across every conversation.
Claude forgets everything
Every session starts from zero. Your preferences, your stack, your conventions.
Context windows expire
The 200k window is big, but temporary. None of it persists.
You repeat yourself
Retyping your setup instructions. Re-explaining your codebase. Again and again.
How it works
From conversation to persistent recall in five steps.
Generates a message or response
Intercepts via tool calls
Classifies the memory type
Embeds and persists locally
Retrieved on next session
Claude
Generates a message or response
MCP
Intercepts via tool calls
Gates
Classifies the memory type
Storage
Embeds and persists locally
Recall
Retrieved on next session
Five memory gates
Every memory is classified through one of five gates, each with its own scope and decay behavior.
Preferences, habits, and workflow patterns.
"I always use tabs over spaces."
People, teams, and social context.
"Sarah is the lead on the auth service."
Facts, knowledge, and technical details.
"Our API uses JWT with RS256 signing."
Commitments and agreed-upon plans.
"We decided to migrate to Postgres next sprint."
Mistakes to avoid and corrections.
"Don't use the legacy endpoint, it's deprecated."
Recall in action
Ask a question. Claude pulls from stored memories and cites its sources.
Your query
What's my preferred database for new projects?
Claude's response
Based on your previous conversations, you prefer PostgreSQL for most projects. You mentioned that your team standardized on Postgres 16 after evaluating alternatives. For quick prototypes, you sometimes reach for SQLite instead.
Recall trace
User prefers PostgreSQL for production databases.
vector94%Team standardized on Postgres 16 after evaluating CockroachDB and PlanetScale.
vector87%Uses SQLite for prototypes and local-first apps.
keyword72%Your memories, your machine.
Choose the storage mode that fits your workflow. Switch anytime.
Cloud
Sign up, add your API key, done. We handle everything else.
Local
SQLite + local embeddings. Zero network calls. Full privacy.
A living identity document
CMK builds a synthesis of who you are as a developer. Updated automatically, always editable.
Identity synthesis
Last updated 2 hours ago
You are a senior TypeScript developer who works primarily with Next.js and PostgreSQL. You prefer functional patterns over class-based code and favor explicit types over inference when the type is not immediately obvious.
Your code style leans minimal: short variable names in tight scopes, descriptive names at module boundaries. You use Tailwind for styling and prefer inline styles with CSS variables for design tokens.
You work on a team of five. Sarah handles auth, Marcus owns the data pipeline, and you lead the frontend and API integration layer.
Get started in seconds
One command to install. Three ways to integrate.
claude mcp add cmk --url https://mcp.cmk.dev/v1 \
--header "Authorization: Bearer <your-api-key>"