Yes, Slivingdoc is free to use.

How do I install Slivingdoc?

Slivingdoc is a local plugin. Install it using npm package: slivingdoc and add the generated configuration snippet to your AI app's MCP config file. Then restart your AI app.

Is Slivingdoc safe to use?

Yes. Slivingdoc passed MCP Marketplace's automated security scan with a score of 10/10 (low risk). Every server on MCP Marketplace is security-scanned before it's listed; see the full security report on this page for the findings and permissions.

What credentials does Slivingdoc need?

Slivingdoc requires the following credentials or environment variables: SLIVINGDOC_TOKEN, SLIVINGDOC_BUCKET, AWS_PROFILE, AWS_REGION, AWS_ENDPOINT_URL_S3, SLIVINGDOC_WORKSPACE_ROOT. You can find setup instructions on the server detail page.

What AI apps work with Slivingdoc?

Slivingdoc uses the Model Context Protocol (MCP) and works with any MCP-compatible AI app, including Claude, ChatGPT / Codex, Gemini, Copilot, Cursor, and more.

Back to Browse

Slivingdoc MCP Server

by Baalimago

Developer ToolsLow Risk10.0MCP RegistryLocal

Free

Server data from the Official MCP Registry

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

About

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

Security Report

10.0

Low Risk10.0Low Risk

Valid MCP server (2 strong, 1 medium validity signals). No known CVEs in dependencies. Package registry verified. Imported from the Official MCP Registry.

12 files analyzed · 1 issue found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

file_system

Check that this permission is expected for this type of plugin.

What You'll Need

Set these up before or after installing:

API token from slivingdoc.dev for hosted storage; use it instead of the bucket and AWS settings, and leave AWS_ENDPOINT_URL_S3 unset.Required

Environment variable: SLIVINGDOC_TOKEN

S3-compatible bucket that stores the shared text workspace. Not needed with SLIVINGDOC_TOKEN, which names its own space.Optional

Environment variable: SLIVINGDOC_BUCKET

Optional AWS profile used by the standard AWS credential chain.Optional

Environment variable: AWS_PROFILE

AWS region for the bucket or S3-compatible endpoint.Optional

Environment variable: AWS_REGION

Optional endpoint for an S3-compatible store such as SeaweedFS.Optional

Environment variable: AWS_ENDPOINT_URL_S3

Optional root that contains directories agents may pull and commit.Optional

Environment variable: SLIVINGDOC_WORKSPACE_ROOT

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-baalimago-slivingdoc": {
      "env": {
        "AWS_REGION": "your-aws-region-here",
        "AWS_PROFILE": "your-aws-profile-here",
        "SLIVINGDOC_TOKEN": "your-slivingdoc-token-here",
        "SLIVINGDOC_BUCKET": "your-slivingdoc-bucket-here",
        "AWS_ENDPOINT_URL_S3": "your-aws-endpoint-url-s3-here",
        "SLIVINGDOC_WORKSPACE_ROOT": "your-slivingdoc-workspace-root-here"
      },
      "args": [
        "-y",
        "slivingdoc",
        "-y"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

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

Reviews

No reviews yet

Be the first to review this server!

4.8

Local

MCP Marketplace

Free

by mcp-marketplace · Developer Tools

Search and install MCP servers from inside your AI client.

Stars

207

Installs