slivingdoc runs on your own machine — the client starts it, so there is no endpoint to ping. 163 installs a week from npm. Last commit 17 Sep 2026.
Share ordinary text files between concurrent agents without silently overwriting edits.
We read the source, 23 h ago · rules 3dff92dd89df
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.
этот файл ставится пользователю, но в репозитории его нет
statePath := filepath.Join(privDir, stateFileName)
const child = spawn(binary, args, { stdio: "inherit", windowsHide: true });
select {
case r := <-results[i]:
i++
return r.data, r.err
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
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.
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": {
"args": [
"-y",
"slivingdoc"
],
"command": "npx"
}
}
}
[mcp_servers.slivingdoc]
command = "npx"
args = ["-y", "slivingdoc"]
{
"mcpServers": {
"slivingdoc": {
"args": [
"-y",
"slivingdoc"
],
"command": "npx"
}
}
}
{
"mcpServers": {
"slivingdoc": {
"args": [
"-y",
"slivingdoc"
],
"command": "npx"
}
}
}
This one needs environment variables set before it will start:
SLIVINGDOC_BUCKET (S3-compatible bucket that stores the shared text workspace.), 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.).
The author declared them in the registry entry; get the values from the project itself.
Coherence guard for shared files: denies stale writes so agents don't silently overwrite each other.
Analyze test coverage from LCOV files - makes AI agents coverage-aware without wasting tokens
Enables coding agents to coordinate edits, reviews, and escalations without file locking conflicts
Move data between 15+ databases, queues and files at high throughput, without it entering context
File-claim coordination for parallel AI coding agents: claim files before edits, no stomping.
Machines share their truth. Confessions made by AI agents: text, a picture, a recording or a film.
Kanban boards, sprints, tickets and a team wiki, with versioned writes for concurrent agents.
Messaging between concurrent AI coding sessions, across clients, over MCP. Zero infrastructure.
Answers built from our own checks of this server.