Browse documentation

Shared memory for agents · alpha

Keep

Agents save, organize, and find documents in one store on your computer, across conversations and projects.

Keep stores documents in collections inside workspaces. A document has a title, a text body, structured JSON data, tags, sources, and links to other documents. Every change keeps a revision, so agents can read history and update records safely.

Run one Keep server and connect every agent to it. Agents then share decisions, notes, and project facts instead of rediscovering them in each conversation.

Install

docker compose up -d

Requirements

  • An x64 computer with Docker Engine and Compose, or Docker Desktop in Linux container mode. The installation guide supplies the Compose files.
  • Or Node.js 24+ for npm install --global @glidermcp/keep@next on Linux x64 (glibc 2.39+), macOS on Apple Silicon, or Windows x64.
  • An MCP client that connects to an HTTP server with a bearer token: the owner token, or a scoped credential for restricted access.

What you can do

  • Keep project decisions and reusable notes available across sessions and agents.
  • Organize text and JSON documents into collections, with optional field schemas.
  • Find records with filters, ranked full-text search, optional local semantic search, and saved views.
  • Count and total structured fields with exact aggregates.
  • Read document history and update records with revision checks, so concurrent agents do not overwrite each other.
  • Pass another authorized agent a record link that follows later edits or pins one revision.
  • Grant each person or agent access to selected workspaces, with expiry and revocation.

Updates

Keep is an alpha. Before an update, stop Keep and back up the complete store directory. A new release upgrades the store schema atomically and preserves content, IDs, and history; an older release may not open an upgraded store. Follow the installation guide for the update steps.

Next steps

Keep runs as one HTTP server, by default on http://127.0.0.1:7340/mcp, and only one Keep process opens a store at a time. The configured token is the owner token: it grants full access to the whole store, so give it only to your own trusted clients. For an agent or person that should see only some workspaces, create a separate scoped credential with the keep CLI; see access administration. Documents stay private: Keep has no public or anonymous access.