slivingdoc
This server gives agents durable, merge-safe shared notes on a notebook directory via two MCP tools, notes_pull and notes_commit.
Pull the notebook (
notes_pull): writes the current notebook into a host directory (default server notebook directory, or a specified absolute path) and records the accepted state so edits can be made locally.Commit changes (
notes_commit): publishes the caller's file edits with a required commit message and incorporates concurrent non-conflicting changes, surfacing conflicts with both versions when the same lines clash.Concurrent editing: supports multiple agents and humans writing to the same notes without pulling first, merging non-overlapping edits Git-style.
Custom workspace location: both tools accept an optional absolute path (up to 4,096 bytes) or fall back to the server's notebook directory, which is reported in results.
Durable shared context: stores UTF-8 text notes (no U+0000) that persist across sessions, with commit messages retained only in recent internal history.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@slivingdoc commit my notes with message 'updated project plan'"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Test coverage: 87.4% ππ
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:
pullandcommit, the rest is handled magicallyYour 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
One binary: "batteries included", as they say
The docs cover
how it works,
the CLI and
configuration;
npx -y slivingdoc serve -h prints every flag.
Related MCP server: Cellar
Get started
Hosted. Sign in at slivingdoc.dev with GitHub or Google then run:
claude mcp add slivingdoc \
-- npx -y slivingdoc serveIt will prompt you to bind a token on initial run.
Free for one space, 10 MB and 250,000 requests a month (pricing).
Self-hosted. Point it at an existing S3-compatible bucket that supports conditional writes.:
export AWS_REGION=eu-north-1
export AWS_ACCESS_KEY_ID=<key>
export AWS_SECRET_ACCESS_KEY=<key>
npx -y slivingdoc serve --bucket my-notesNo bucket yet? examples/seaweedfs/ runs one
locally in a container, and terraform/ provisions one on AWS.
As stdio MCP client
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:
npx -y slivingdoc versionnpx fetches and verifies the native binary on first run. You can also
install the matching binary with the checksummed setup script:
curl -fsSL https://raw.githubusercontent.com/baalimago/slivingdoc/refs/heads/master/setup.sh | shIt installs into $HOME/.local/bin (or /usr/local/bin when run as root).
Then run:
slivingdoc login
slivingdoc pull notes
echo "hello from $(hostname)" > notes/hello.md
slivingdoc commit notes -m "First note"Development
AGENTS.md is the developer guide and
architecture/ holds the contract, one concern
per file.
make qa # lint plus the full Go and npm test suitesLicense
MIT, see LICENSE. Third-party notices for the statically linked libgit2 are in NOTICE.
Not affiliated with Paris Hilton.
Available Tools
2 toolsnotes_commitA
Publish the caller's changes in the notebook directory and incorporate concurrent non-conflicting changes. Omit path or pass an empty string to use the server's notebook directory, which the result reports. message must be non-blank UTF-8 without U+0000, at most 16,384 bytes; it is retained in recent internal history only.
Inputs: message (required), path.
notes_pullA
Write the current notebook into the notebook directory and record the accepted state. Omit path or pass an empty string to use the server's notebook directory, which the result reports. Edit UTF-8 text files (without U+0000) there between notes_pull and notes_commit; notes_commit publishes the changes and incorporates concurrent non-conflicting changes.
Inputs: path.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogβ¦
TDQS
Scored across 2 tools
notes_commit and notes_pull have clearly distinct purposes: one publishes local changes and incorporates concurrent changes, the other writes the current notebook into the directory. Their descriptions make the boundary unambiguous.
Both tools follow a consistent notes_<verb> snake_case pattern. There are no deviations or mixed conventions.
With only two tools, the set is borderline thin for a notebook version control system. While each tool earns its place, typical workflows require more operations.
The toolset covers only pull and commit, missing critical operations such as conflict resolution, status, history, and initialization. These significant gaps will cause agent failures in realistic use.
Maintenance
Related MCP Connectors
A MCP server built for developers enabling Git based project management with project and personalβ¦
One MCP server for all your MCP servers: code mode, per-tool permissions, approvals and audit.
System-of-record notebook for AI coding agents: pages, datastores, tasks, skills over MCP.
Remote MCP server for notes, tasks, kanban boards and docs - the Slates agentic workspace
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA secure and scalable Git MCP server giving AI agents powerful version control for local and (soon) serverless environments.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceAn interactive notebook server that enables humans and AI agents to collaboratively edit and run Jupyter notebooks on a shared kernel, with real-time streaming and automatic MCP integration for agent access.16 npmMIT
- AlicenseNot gradedqualityDmaintenanceA storage-backed MCP server for sharing durable project context between trusted coding agents, with project discovery, optimistic concurrency, and timestamped handoffs.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceAn MCP server that gives AI agents a full, safe interface to Git with automatic backups, isolated worktrees, and structured JSON outputs.46MIT