Slivingdoc MCP Server

Slivingdoc is an MCP integration. Durable context for agents and people: shared notes with Git-style merges, no silent overwrites.

Packages and local setup

The published npm package is slivingdoc, version 1.0.3. Its declared MCP transport is stdio.

The package declares 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..

This package has launch arguments in its registry record. Use the maintainer’s configuration for those arguments rather than launching it with only the package name.

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 1.0.3 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related other integrations MCP servers for tools that cover the same kind of work.