Slivingdoc

by io.github.baalimago

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

接入你的智能体

添加此服务器

The publisher's own command. Not a PlugMCP endpoint.

Local command

npx -y [email protected]

Credentials from the publisher

SLIVINGDOC_TOKEN — 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.

Provider

Claude Code

SLIVINGDOC_TOKEN=<secret> SLIVINGDOC_BUCKET=<value> AWS_PROFILE=<value> AWS_REGION=<value> AWS_ENDPOINT_URL_S3=<value> SLIVINGDOC_WORKSPACE_ROOT=<value> claude mcp add io.github.baalimago-slivingdoc -- npx -y [email protected]

Run in a terminal.

Claude Desktop

{
  "mcpServers": {
    "io.github.baalimago-slivingdoc": {
      "command": "npx",
      "args": [
        "-y",
        "[email protected]"
      ],
      "env": {
        "SLIVINGDOC_TOKEN": "<secret>",
        "SLIVINGDOC_BUCKET": "<value>",
        "AWS_PROFILE": "<value>",
        "AWS_REGION": "<value>",
        "AWS_ENDPOINT_URL_S3": "<value>",
        "SLIVINGDOC_WORKSPACE_ROOT": "<value>"
      }
    }
  }
}

claude_desktop_config.json

Step-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

在 PlugMCP 上运行

用我们的密钥与日志托管一份副本。

这是你新建的服务器，不是此条目的官方端点。若要用发布方的 URL 与凭证，请使用上方安装面板。

启动

Related MCP

Related skills

View all

Questions

How do I install Slivingdoc?: Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
Does Slivingdoc need an API key?: The publisher lists these environment variables: SLIVINGDOC_TOKEN, SLIVINGDOC_BUCKET, AWS_PROFILE, AWS_REGION, AWS_ENDPOINT_URL_S3, SLIVINGDOC_WORKSPACE_ROOT.
What transport does Slivingdoc use?: Slivingdoc runs locally over stdio.
When was Slivingdoc last checked?: Last checked 2026-10-16. Durable context for agents and people: shared notes with Git-style merges, no silent overwrites.

Test coverage: 89.1% 😍👌

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.

添加此服务器

The publisher's own command. Not a PlugMCP endpoint.

Credentials from the publisher

SLIVINGDOC_TOKEN — 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.

Provider

Claude Code

SLIVINGDOC_TOKEN=<secret> SLIVINGDOC_BUCKET=<value> AWS_PROFILE=<value> AWS_REGION=<value> AWS_ENDPOINT_URL_S3=<value> SLIVINGDOC_WORKSPACE_ROOT=<value> claude mcp add io.github.baalimago-slivingdoc -- npx -y [email protected]

Run in a terminal.

Claude Desktop

{
  "mcpServers": {
    "io.github.baalimago-slivingdoc": {
      "command": "npx",
      "args": [
        "-y",
        "[email protected]"
      ],
      "env": {
        "SLIVINGDOC_TOKEN": "<secret>",
        "SLIVINGDOC_BUCKET": "<value>",
        "AWS_PROFILE": "<value>",
        "AWS_REGION": "<value>",
        "AWS_ENDPOINT_URL_S3": "<value>",
        "SLIVINGDOC_WORKSPACE_ROOT": "<value>"
      }
    }
  }
}

claude_desktop_config.json

Step-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Questions

How do I install Slivingdoc?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Slivingdoc need an API key?

The publisher lists these environment variables: SLIVINGDOC_TOKEN, SLIVINGDOC_BUCKET, AWS_PROFILE, AWS_REGION, AWS_ENDPOINT_URL_S3, SLIVINGDOC_WORKSPACE_ROOT.

What transport does Slivingdoc use?

Slivingdoc runs locally over stdio.

When was Slivingdoc last checked?

Last checked 2026-10-16. Durable context for agents and people: shared notes with Git-style merges, no silent overwrites.

Test coverage: 89.1% 😍👌

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.