slivingdoc

mcp
Guvenlik Denetimi
Basarisiz
Health Uyari
  • License — License: MIT
  • Description — Repository has a description
  • Active repo — Last push 0 days ago
  • Low visibility — Only 6 GitHub stars
Code Basarisiz
  • exec() — Shell command execution in npm/slivingdoc/lib/install.mjs
  • process.env — Environment variable access in npm/slivingdoc/lib/launcher.mjs
  • exec() — Shell command execution in npm/slivingdoc/lib/sums.mjs
Permissions Gecti
  • Permissions — No dangerous permissions requested

Bu listing icin henuz AI raporu yok.

SUMMARY

Write in parallel. Persist to s3.

README.md

Test coverage: 88.9% 😍👌

slivingdoc banner

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

Two panes: you on the command line, an agent calling notes_pull and notes_commit over MCP. You change one line of plan.md and the agent another; both commit without pulling first and both land, merged. Then both change the same line: the agent commits first, and your commit returns CONTENT_CONFLICT with both versions in the file.

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: pull and commit, 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.

Yorumlar (0)

Sonuc bulunamadi