mcpField
S
slivingdoc

slivingdoc

Local
slivingdoc.devMemory & Knowledge7Updated 1d ago
RepositoryVisit website

About slivingdoc

slivingdoc is a shared durable-notes service for agents and people, with concurrent updates handled through Git-style merges rather than silent overwrites. It can use an S3-compatible bucket or a hosted space, with access controls for reading and writing.

Key features

  1. 01Durable shared notes
  2. 02Git-style merging for concurrent writes
  3. 03S3-compatible or hosted storage
  4. 04Read and write access controls
  5. 05CLI and single-binary distribution

Use cases

  1. 01Share context across agent sessions
  2. 02Coordinate concurrent edits to notes
  3. 03Store team notes in an S3-compatible bucket

MCP support

It runs as an MCP server over stdio and lets MCP clients pull and commit shared notes. Hosted use supports token authentication or browser-based sign-in.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "baalimago-slivingdoc": {
      "command": "npx",
      "args": [
        "-y",
        "slivingdoc"
      ],
      "env": {
        "SLIVINGDOC_TOKEN": "<SLIVINGDOC_TOKEN>",
        "SLIVINGDOC_BUCKET": "<SLIVINGDOC_BUCKET>",
        "AWS_PROFILE": "<AWS_PROFILE>",
        "AWS_REGION": "<AWS_REGION>",
        "AWS_ENDPOINT_URL_S3": "<AWS_ENDPOINT_URL_S3>",
        "SLIVINGDOC_WORKSPACE_ROOT": "<SLIVINGDOC_WORKSPACE_ROOT>"
      }
    }
  }
}
Run commandnpx -y slivingdoc
Environment variables to set
SLIVINGDOC_TOKENSecretAPI token from slivingdoc.dev for hosted storage; use it instead of the bucket and AWS settings, and leave AWS_ENDPOINT_URL_S3 unset.
SLIVINGDOC_BUCKETS3-compatible bucket that stores the shared text workspace. Not needed with SLIVINGDOC_TOKEN, which names its own space.
AWS_PROFILEOptional AWS profile used by the standard AWS credential chain.
AWS_REGIONAWS region for the bucket or S3-compatible endpoint.
AWS_ENDPOINT_URL_S3Optional endpoint for an S3-compatible store such as SeaweedFS.
SLIVINGDOC_WORKSPACE_ROOTOptional root that contains directories agents may pull and commit.

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npmslivingdoc1.3.1

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

Test coverage: 87.4% 😍👌

slivingdoc banner

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

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

Or skip the token: npx -y slivingdoc serve with no credential signs in on first use. The first tool call answers with an approval page to open in the browser, and every later server on the machine uses that login (--login never turns this off).

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.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.