Early days. Memcrate ships Claude Code integration today. Cursor, Cowork, Aider, and an MCP server are on the roadmap — see the repo for status.

Welcome to Memcrate

Memcrate is a personal context vault for AI tools — a folder of markdown on your disk that any AI assistant can read, write to, and reason about.

It gives you three commands across every supported tool:

  • /save — write the current session into a structured log
  • /pin — promote a fact from the session into your permanent context
  • /load — start a fresh session already oriented to who you are and what you’re working on

No cloud. No vendor lock-in. Just a folder you own.


Start here

The fastest path from zero to “your AI knows who I am”:

  1. Install the CLI — single static binary, three platforms
  2. Quick start — scaffold a vault and use the verbs in five minutes
  3. The vault — what’s in the folder, and why
  4. The verbs — what /save, /pin, and /load actually do
  5. Claude Code integration — the one tool with skills today

How it works

Memcrate has three pieces:

  1. A vault format — a small, opinionated markdown directory shape (Core/Context/Profile.md, Core/Sessions/, etc.) that’s both human-readable and machine-readable.
  2. A CLImemcrate init scaffolds a vault, memcrate setup walks you through the starter files, memcrate install <tool> drops the per-tool integrations into place.
  3. Skills (per tool) — for each supported AI tool, Memcrate ships a small integration that wires up the three verbs. Today that’s Claude Code; more are on the roadmap.

The vault is the source of truth. The CLI and skills exist to keep it consistent and to let your AI tools work with it.


Where is this going?

Memcrate is v0.3 — usable, stable, and shipping. The near-term focus is widening tool support:

  • Cursor.cursorrules template that wires natural-language verb patterns
  • Cowork — packaged skill that uploads via the Cowork UI
  • Aider.aider.conf.yml rewriter that adds the canonical context files
  • MCPmcp-memcrate server exposing vault_save, vault_pin, vault_load, vault_search

Until those land, the vault format itself is the stable surface. You can read it with anything — even tools without a Memcrate integration will benefit from being pointed at the canonical files.