slivingdoc runs on your own machine — the client starts it, so there is no endpoint to ping. 764 installs a week from npm. Last commit 27 Oct 2026.
Durable context for agents and people: shared notes with Git-style merges, no silent overwrites.
What the code does
We read the source, 6 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const child = spawn(binary, args, { stdio: "inherit", windowsHide: true });
Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.
statePath := filepath.Join(privDir, stateFileName)
select {
case r := <-results[i]:
i++
return r.data, r.err
socks := []string{"/var/run/docker.sock"}
S3 flag, an AWS variable, an existing ~/.aws/credentials or ~/.aws/config
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add slivingdoc -- npx -y slivingdoc{
"mcpServers": {
"slivingdoc": {
"command": "npx",
"args": [
"-y",
"slivingdoc"
]
}
}
}[mcp_servers.slivingdoc]
command = "npx"
args = ["-y", "slivingdoc"]{
"mcpServers": {
"slivingdoc": {
"command": "npx",
"args": [
"-y",
"slivingdoc"
]
}
}
}{
"servers": {
"slivingdoc": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"slivingdoc"
]
}
}
}Optional settings from the registry entry, left out of the block above:
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).
Alternatives to slivingdoc
same job, measured the same wayShared rooms and durable notes for agents over plain HTTP: rendezvous, hand-off, coordination.
Shared docs for people and their agents: markdown docs and HTML pages with comments and history.
Coherence guard for shared files: denies stale writes so agents don't silently overwrite each other.
Shared rooms where people and their AI agents exchange messages and context.
Shared, living memory for you and your people — coves your AI assistant can read and write.
One record of code, files and pages that people and agents read and write, with lanes and git.
Shared workspaces of typed objects with views, changes and sharing, for AI agents and people.
Encrypted mail, shared memory, and persistent context for AI agents.
slivingdoc — questions
Answers built from our own checks of this server.