Durable context for agents and people: shared notes with Git-style merges, no silent overwrites.
To add slivingdoc to Claude, run the install command below or copy the ready-made config for Claude Code, Claude Desktop, Cursor and VS Code further down. Restart your client after adding it and its tools show up in your next conversation. It needs 6 environment variables, listed below.
Install
npx -y slivingdoc@1.3.1Environment variables
SLIVINGDOC_TOKENSet in your MCP configSLIVINGDOC_BUCKETSet in your MCP configAWS_PROFILESet in your MCP configAWS_REGIONSet in your MCP configAWS_ENDPOINT_URL_S3Set in your MCP configSLIVINGDOC_WORKSPACE_ROOTSet in your MCP configInstall with your client
claude mcp add slivingdoc --env SLIVINGDOC_TOKEN=<YOUR_SLIVINGDOC_TOKEN> --env SLIVINGDOC_BUCKET=<YOUR_SLIVINGDOC_BUCKET> --env AWS_PROFILE=<YOUR_AWS_PROFILE> --env AWS_REGION=<YOUR_AWS_REGION> --env AWS_ENDPOINT_URL_S3=<YOUR_AWS_ENDPOINT_URL_S3> --env SLIVINGDOC_WORKSPACE_ROOT=<YOUR_SLIVINGDOC_WORKSPACE_ROOT> -- npx -y slivingdoc@1.3.1
Run this in a terminal to add the server to Claude Code.
What this does
slivingdoc exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.
Requirements
This server needs the following environment variables to be set before it can run:
SLIVINGDOC_TOKEN SLIVINGDOC_BUCKET AWS_PROFILE AWS_REGION AWS_ENDPOINT_URL_S3 SLIVINGDOC_WORKSPACE_ROOT
Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).
Frequently asked questions
How do I install slivingdoc?
Run the Claude Code command in the install section to add slivingdoc to Claude Code, or copy the ready-made config for your client from the install section on this page. Restart your client afterwards and the tools appear in your next conversation.
Which clients work with slivingdoc?
This page carries setup and config for Claude Code, Claude Desktop, Cursor and VS Code. Any other MCP client that accepts a standard server config can connect to slivingdoc as well.
Does slivingdoc need an API key?
Yes. Before it can run, set these environment variables: SLIVINGDOC_TOKEN, SLIVINGDOC_BUCKET, AWS_PROFILE, AWS_REGION, AWS_ENDPOINT_URL_S3, SLIVINGDOC_WORKSPACE_ROOT. They go in the env block of your MCP config.
Imported from the Official MCP Registry. The details above come from the registry entry; the maker can claim this listing to correct them, add docs, and see its traffic.
Is this your MCP server?
Claim this listing to see its traffic, fix details yourself, and skip the review queue on future updates.
Add this badge to your README
Show visitors this server is listed in the ClaudeRules directory. The badge links straight to this listing.
[](https://clauderules.net/mcp/io-github-baalimago-slivingdoc)<a href="https://clauderules.net/mcp/io-github-baalimago-slivingdoc" target="_blank" rel="noopener noreferrer"><img src="https://clauderules.net/api/badge/io-github-baalimago-slivingdoc" alt="Listed on clauderules.net" /></a>More DevTools MCP servers
Awesome MCP Servers by punkpeye
A curated, community-maintained list of Model Context Protocol (MCP) servers, organized by category, with sections for MCP clients, tutorials, and community resources. The repository is a directory of production-ready and experimental servers that extend AI capabilities through file access, database connections, and API integrations; it is a list, not a runnable MCP server itself.
GitHub
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
FastMCP
🐍 - A high-level framework for building MCP servers in Python
Serena MCP: the IDE for your agent
A powerful toolkit for coding, providing semantic retrieval and editing capabilities.