Skip to main content
MCP server CX Codex

slivingdoc — Claude Code MCP server: shared agent notes

Keeps agent context in plain text files that several sessions read and write at once. Merges edits instead of overwriting them.

Install into Claude Code · Platform CLI All methods and platforms ↓
claude mcp add --env SLIVINGDOC_TOKEN=<SLIVINGDOC_TOKEN> --env SLIVINGDOC_BUCKET=<SLIVINGDOC_BUCKET> --env AWS_PROFILE=<AWS_PROFILE> --env AWS_REGION=<AWS_REGION> --env AWS_ENDPOINT_URL_S3=<AWS_ENDPOINT_URL_S3> --transport stdio slivingdoc -- npx -y slivingdoc
Open on GitHub

What slivingdoc does

slivingdoc gives agents a shared store of notes. Files live in an S3-compatible bucket, agents call pull and commit, and overlapping edits merge the way Git does. When two writers touch the same line, the later commit comes back as CONTENT_CONFLICT with both versions left in the file. Nothing gets silently dropped.

Setup runs through npx, which fetches the native binary on first use. You can host on slivingdoc.dev: sign in with GitHub or Google, create a token, and the free tier covers one space. A bucket of your own works too, but it has to support conditional writes — without that, concurrent commits won't land. The repo ships a SeaweedFS example in a container if you want to try it locally first.

ACLs decide where agents may read and where they may write. The interface stays narrow on purpose: slivingdoc stores notes, it doesn't write them for you.

What it helps with

  • carry agent context across sessions so it survives restarts
  • let several agents write to the same notes without losing edits
  • split read and write permissions across spaces
  • run the note store in your own S3 bucket
  • inspect a merge conflict directly in the file

Example prompts for the agent

  • Pull the notes from slivingdoc and pick up where we left off
  • Write the refactor plan to plan.md and commit it
  • Show me what changed in the notes since the last commit

How to install slivingdoc

Platform CLI

claude mcp add --env SLIVINGDOC_TOKEN=<SLIVINGDOC_TOKEN> --env SLIVINGDOC_BUCKET=<SLIVINGDOC_BUCKET> --env AWS_PROFILE=<AWS_PROFILE> --env AWS_REGION=<AWS_REGION> --env AWS_ENDPOINT_URL_S3=<AWS_ENDPOINT_URL_S3> --transport stdio slivingdoc -- npx -y slivingdoc

Replace <…> with your own values. 1 more environment variable is in the server README

Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more

Questions about slivingdoc

How do I install slivingdoc in Claude Code?

For the hosted option: claude mcp add slivingdoc -e SLIVINGDOC_TOKEN=<SLIVINGDOC_TOKEN> -- npx -y slivingdoc. For your own bucket, add SLIVINGDOC_BUCKET, AWS_PROFILE, AWS_REGION and AWS_ENDPOINT_URL_S3.

What does slivingdoc do?

It stores agent notes as text files and merges simultaneous edits rather than overwriting them. It runs as an MCP server or as a CLI.

What kind of bucket does self-hosting need?

An S3-compatible one that supports conditional writes. Concurrent commits fail without it.

Similar MCP servers

All MCP servers for Agent setup: memory, context, orchestration →

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor