# Introduction

> What slivingdoc is, its two operations, who it is for, and where to go next.

Canonical URL: https://www.slivingdoc.dev/docs/v0.1/ · Version: 0.1 · Updated: 2026-09-26

Full site index: https://www.slivingdoc.dev/llms.txt

slivingdoc is durable context for agents: a distributed notebook built
for high-scale agent fleets.
A server exposes it over the Model Context Protocol (MCP), and the same
two operations are available directly to humans from the command line, so
agents and people can share one notebook without agreeing on a protocol
between them: they read and write the same files with the tools they
already have.

Notes live either in hosted storage on slivingdoc.dev or in an
S3-compatible bucket of your own. Concurrent writers never overwrite
one another's accepted work — a commit that conflicts with the remote
state returns the conflict instead of silently losing it. See
[Guarantees and limits](/docs/v0.1/concepts/guarantees/) for the accepted
contract behind that claim.

## Two ways to store notes

- **Hosted.** [Sign in](/login), name a space, and create a token; the
  site gives you a snippet to paste into your MCP host or shell. There is
  no bucket to run. This needs slivingdoc 0.2.0 or newer. The free plan
  needs no card, and
  [Pricing](/pricing/) lists its limits.
- **Your own bucket.** Point slivingdoc at an S3-compatible bucket and
  give it credentials through the normal AWS chain. See
  [Set up a bucket](/docs/v0.1/guides/bucket/).

The commands and the publication protocol are the same either way; a
token in `SLIVINGDOC_TOKEN` is what selects hosted storage. The
[Quickstart](/docs/v0.1/quickstart/) covers both.

## The two operations

| Operation | MCP tool       | CLI command | Effect                                                                            |
| --------- | -------------- | ----------- | --------------------------------------------------------------------------------- |
| Pull      | `notes_pull`   | `pull`      | Write the current notebook into a directory.                                      |
| Commit    | `notes_commit` | `commit`    | Publish local changes, merging in any concurrent, non-conflicting remote changes. |

An MCP server takes its own private notebook directory by default, so
nothing has to be configured or coordinated between agents; a fixed,
shared directory is also available for humans and agents to edit
together. See [Connect an MCP host](/docs/v0.1/guides/mcp-hosts/) and
[Use the CLI without a host](/docs/v0.1/guides/cli/).

## Who it is for

- **Agentic harnesses** that want a shared, durable place for agents to
  keep notes, plans, or a shared knowledge base, reachable over MCP with
  no server of your own to run.
- **Fleets of agents** working from one space or bucket, where conflicting writes
  must be caught rather than silently dropped.
- **Humans and agents sharing a directory**, editing the same files with
  whatever tools they already use.

## Where to go next

- New to slivingdoc? Start with [Quickstart](/docs/v0.1/quickstart/).
- Configuring a real deployment? See
  [Configuration](/docs/v0.1/reference/configuration/) for every flag,
  environment variable, and default.
- Setting up storage? [Sign in](/login) for hosted storage, or see
  [Set up a bucket](/docs/v0.1/guides/bucket/) to run your own.