Durable context for agents and people: shared notes with Git-style merges, no silent overwrites.
io.github.baalimago/slivingdoc MCP Server
The MCP server “io.github.baalimago/slivingdoc” shares ordinary text files between concurrent agents without silently overwriting edits. It provides “slivingdoc” functionality for notes management, including Gitlike semantics, automatic conflict resolution, and high-speed processing suitable for parallelism.
🛠️ Key Features
Gitlike semantics using familiar terminology (slivingdoc)
Automatic conflict resolution: commits are accepted only after conflicts are resolved
High speed processing designed for high scale and parallelism
Plug-and-play setup (bucket-based configuration is referenced)
🚀 Use Cases
Notes/tool workflows where multiple agents edit the same ordinary text files
Scenarios requiring prevention of silent overwrites during concurrent updates
⚡ Developer Benefits
Trust-based behavior: conflicts must be resolved before changes are accepted
Designed for parallel agent operation
Test coverage reported at 83.0%
⚠️ Limitations
The provided source excerpt does not describe authentication, storage backends beyond a “bucket,” or supported file formats beyond “ordinary text files.”
Durable context that outlives every session: plain text files that
fleets of agents (and their humans) pull and commit at the same time,
with Git-style merges instead of overwrites.
Store them durably in your own S3-compatible bucket, or let
slivingdoc.dev host them, free to
start.
Two panes: you on the command line, an agent calling notes_pull and notes_commit over MCP. You change one line of plan.md and the agent another; both commit without pulling first and both land, merged. Then both change the same line: the agent commits first, and your commit returns CONTENT_CONFLICT with both versions in the file.
Features
Durable context: automatically store agent's context
Merge-safe concurrent writes: move fast with no fear
Edits outsourced: slivingdoc concerns itself with storing, not writing
Simple interface:pull and commit, the rest is handled magically
Your bucket or ours: any S3-compatible bucket, or a hosted space you
can share with invite links
Powerful yet simple ACL: you decide where agents can read, where they can write
See MCP hosts for how to configure the MCP
server in your agentic coder. The same system applies in the openai agent SDK (and any other LLM engine with MCP client support).
As CLI
"Install" it via npx:
sh
npx -y slivingdoc version
npx fetches and verifies the native binary on first run. You can also
install the matching binary with the checksummed setup script:
sh
curl -fsSL https://raw.githubusercontent.com/baalimago/slivingdoc/refs/heads/master/setup.sh | sh
It installs into $HOME/.local/bin (or /usr/local/bin when run as root).