slivingdoc
Durable context for agents and people: shared notes with Git-style merges, no silent overwrites.
Que pouvez-vous faire avec slivingdoc ?
- 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:
pullandcommit, the rest is handled magically - Your bucket or ours: any S3-compatible bucket, or a hosted space you
- Powerful yet simple ACL: you decide where agents can read, where they can write
- One binary: "batteries included", as they say
Installation
Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).
slivingdocclaude mcp add slivingdoc -e 'SLIVINGDOC_TOKEN=<your slivingdoc_token>' -e 'SLIVINGDOC_BUCKET=<SLIVINGDOC_BUCKET>' -e 'AWS_PROFILE=<AWS_PROFILE>' -e 'AWS_REGION=us-east-1' -e 'AWS_ENDPOINT_URL_S3=<AWS_ENDPOINT_URL_S3>' -e 'SLIVINGDOC_WORKSPACE_ROOT=<SLIVINGDOC_WORKSPACE_ROOT>' -- npx -y slivingdoc@1.2.0 serve
{
"mcpServers": {
"slivingdoc": {
"command": "npx",
"args": [
"-y",
"slivingdoc@1.2.0",
"serve"
],
"env": {
"SLIVINGDOC_TOKEN": "<your slivingdoc_token>",
"SLIVINGDOC_BUCKET": "<SLIVINGDOC_BUCKET>",
"AWS_PROFILE": "<AWS_PROFILE>",
"AWS_REGION": "us-east-1",
"AWS_ENDPOINT_URL_S3": "<AWS_ENDPOINT_URL_S3>",
"SLIVINGDOC_WORKSPACE_ROOT": "<SLIVINGDOC_WORKSPACE_ROOT>"
}
}
}
}
Variables d'environnement
SLIVINGDOC_TOKENsecret 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_BUCKETS3-compatible bucket that stores the shared text workspace. Not needed with SLIVINGDOC_TOKEN, which names its own space.AWS_PROFILEOptional AWS profile used by the standard AWS credential chain.AWS_REGIONAWS region for the bucket or S3-compatible endpoint.AWS_ENDPOINT_URL_S3Optional endpoint for an S3-compatible store such as SeaweedFS.SLIVINGDOC_WORKSPACE_ROOTOptional root that contains directories agents may pull and commit.
Documentation
Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.
Test coverage: 87.5% 😍👌
Shared notes for your agents.
Durable context that outlives every session: plain text files that fleets of agents (and their humans) pull and commit at the same time, with Git-style merges instead of overwrites. Store them durably in your own S3-compatible bucket, or let slivingdoc.dev host them, free to start.
Website · Docs · Pricing · Architecture
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:
pullandcommit, 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.
Questions fréquentes
Qu'est-ce que slivingdoc ?
Durable context for agents and people: shared notes with Git-style merges, no silent overwrites.
Comment installer slivingdoc ?
Il s'exécute sur votre machine. Dans Claude Code : claude mcp add slivingdoc -e 'SLIVINGDOC_TOKEN=<your slivingdoc_token>' -e 'SLIVINGDOC_BUCKET=<SLIVINGDOC_BUCKET>' -e 'AWS_PROFILE=<AWS_PROFILE>' -e 'AWS_REGION=us-east-1' -e 'AWS_ENDPOINT_URL_S3=<AWS_ENDPOINT_URL_S3>' -e 'SLIVINGDOC_WORKSPACE_ROOT=<SLIVINGDOC_WORKSPACE_ROOT>' -- npx -y slivingdoc@1.2.0 serve. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.
Faut-il une clé API pour slivingdoc ?
Oui. Il attend SLIVINGDOC_TOKEN, à renseigner dans sa configuration.
slivingdoc est-il open source ?
Oui. Son code est sur GitHub sous licence MIT.
Qui maintient slivingdoc ?
Il est publié par baalimago. AI.tn le référence sans le maintenir ni le recommander.
Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.