English Français العربية

slivingdoc

Official registry Developer tools

Durable context for agents and people: shared notes with Git-style merges, no silent overwrites.

Source code Website Documentation

What can you do with slivingdoc?

  • 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
  • Powerful yet simple ACL: you decide where agents can read, where they can write
  • One binary: "batteries included", as they say

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

NPM package slivingdoc
Claude Code 
claude mcp add slivingdoc -e 'SLIVINGDOC_TOKEN=<your slivingdoc_token>' -e 'SLIVINGDOC_BUCKET=<SLIVINGDOC_BUCKET>' -e 'AWS_PROFILE=<AWS_PROFILE>' -e 'AWS_REGION=us-east-1' -e 'AWS_ENDPOINT_URL_S3=<AWS_ENDPOINT_URL_S3>' -e 'SLIVINGDOC_WORKSPACE_ROOT=<SLIVINGDOC_WORKSPACE_ROOT>' -- npx -y slivingdoc@1.2.0 serve
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "slivingdoc": {
            "command": "npx",
            "args": [
                "-y",
                "slivingdoc@1.2.0",
                "serve"
            ],
            "env": {
                "SLIVINGDOC_TOKEN": "<your slivingdoc_token>",
                "SLIVINGDOC_BUCKET": "<SLIVINGDOC_BUCKET>",
                "AWS_PROFILE": "<AWS_PROFILE>",
                "AWS_REGION": "us-east-1",
                "AWS_ENDPOINT_URL_S3": "<AWS_ENDPOINT_URL_S3>",
                "SLIVINGDOC_WORKSPACE_ROOT": "<SLIVINGDOC_WORKSPACE_ROOT>"
            }
        }
    }
}

Environment variables

  • SLIVINGDOC_TOKEN secret API token from slivingdoc.dev for hosted storage; use it instead of the bucket and AWS settings, and leave AWS_ENDPOINT_URL_S3 unset.
  • SLIVINGDOC_BUCKET S3-compatible bucket that stores the shared text workspace. Not needed with SLIVINGDOC_TOKEN, which names its own space.
  • AWS_PROFILE Optional AWS profile used by the standard AWS credential chain.
  • AWS_REGION AWS region for the bucket or S3-compatible endpoint.
  • AWS_ENDPOINT_URL_S3 Optional endpoint for an S3-compatible store such as SeaweedFS.
  • SLIVINGDOC_WORKSPACE_ROOT Optional root that contains directories agents may pull and commit.

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. Features
  2. Get started
  3. Development
  4. License

Test coverage: 87.5% 😍👌

Shared notes for your agents.

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.

Website · Docs · Pricing · Architecture

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
  • 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.

Get started

Hosted. Sign in at slivingdoc.dev with GitHub or Google, create a token, and add the server to your agent:

claude mcp add slivingdoc \
  --env SLIVINGDOC_TOKEN=<your-api-token> \
  -- npx -y slivingdoc serve

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-notes

No 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 version

npx 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/setup.sh | sh

It installs into $HOME/.local/bin (or /usr/local/bin when run as root).

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 suites

License

MIT, see LICENSE. Third-party notices for the statically linked libgit2 are in NOTICE.

Not affiliated with Paris Hilton.

Frequently asked questions

What is slivingdoc?

Durable context for agents and people: shared notes with Git-style merges, no silent overwrites.

How do I install slivingdoc?

It runs on your machine. In Claude Code: claude mcp add slivingdoc -e 'SLIVINGDOC_TOKEN=<your slivingdoc_token>' -e 'SLIVINGDOC_BUCKET=<SLIVINGDOC_BUCKET>' -e 'AWS_PROFILE=<AWS_PROFILE>' -e 'AWS_REGION=us-east-1' -e 'AWS_ENDPOINT_URL_S3=<AWS_ENDPOINT_URL_S3>' -e 'SLIVINGDOC_WORKSPACE_ROOT=<SLIVINGDOC_WORKSPACE_ROOT>' -- npx -y slivingdoc@1.2.0 serve. For other clients, paste the JSON configuration from this page into their MCP settings.

Does slivingdoc need an API key?

Yes. It expects SLIVINGDOC_TOKEN, which you set in its configuration.

Is slivingdoc open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains slivingdoc?

It is published by baalimago. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.