Agent-Native Calendar
Agent-Native Google Calendar - manage events, sync, and public booking
Description from the maker (original English)
Durable context for agents and people: shared notes with Git-style merges, no silent overwrites.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
SLIVINGDOC_TOKEN, SLIVINGDOC_BUCKET, AWS_PROFILE, AWS_REGION, AWS_ENDPOINT_URL_S3, SLIVINGDOC_WORKSPACE_ROOTValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"slivingdoc": {
"command": "npx",
"args": [
"-y",
"slivingdoc",
"serve"
],
"env": {
"SLIVINGDOC_TOKEN": "your-value",
"SLIVINGDOC_BUCKET": "your-value",
"AWS_PROFILE": "your-value",
"AWS_REGION": "your-value",
"AWS_ENDPOINT_URL_S3": "your-value",
"SLIVINGDOC_WORKSPACE_ROOT": "your-value"
}
}
}
}Run this in your terminal
claude mcp add slivingdoc --env SLIVINGDOC_TOKEN=your-value --env SLIVINGDOC_BUCKET=your-value --env AWS_PROFILE=your-value --env AWS_REGION=your-value --env AWS_ENDPOINT_URL_S3=your-value --env SLIVINGDOC_WORKSPACE_ROOT=your-value -- npx -y slivingdoc serveFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"slivingdoc": {
"command": "npx",
"args": [
"-y",
"slivingdoc",
"serve"
],
"env": {
"SLIVINGDOC_TOKEN": "your-value",
"SLIVINGDOC_BUCKET": "your-value",
"AWS_PROFILE": "your-value",
"AWS_REGION": "your-value",
"AWS_ENDPOINT_URL_S3": "your-value",
"SLIVINGDOC_WORKSPACE_ROOT": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"slivingdoc": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"slivingdoc",
"serve"
],
"env": {
"SLIVINGDOC_TOKEN": "your-value",
"SLIVINGDOC_BUCKET": "your-value",
"AWS_PROFILE": "your-value",
"AWS_REGION": "your-value",
"AWS_ENDPOINT_URL_S3": "your-value",
"SLIVINGDOC_WORKSPACE_ROOT": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
SLIVINGDOC_BUCKET envAWS_PROFILE envAWS_REGION envAWS_ENDPOINT_URL_S3 envSLIVINGDOC_WORKSPACE_ROOT envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account baalimago, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: SLIVINGDOC_TOKEN
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (1.3.1) reached the registry 10 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Agent-Native Calendar, Excel MCP Server, MCP Server for Excel
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Agent-Native Google Calendar - manage events, sync, and public booking
Lets AI create and edit Excel files itself, including formulas, charts and PivotTables, without Excel installed.
Excel automation for AI - Sheets, Power Query, DAX, VBA, Tables, Ranges and more. Windows only.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Test coverage: 87.4% 😍👌
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
pull and commit, the rest is handled magicallyThe docs cover how it works, the CLI and configuration; npx -y slivingdoc serve -h prints every flag.
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= \ -- npx -y slivingdoc serve
Or skip the token: npx -y slivingdoc serve with no credential signs in on first use. The first tool call answers with an approval page to open in the browser, and every later server on the machine uses that login (--login never turns this off).
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= export AWS_SECRET_ACCESS_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.
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).
"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"
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
MIT, see LICENSE. Third-party notices for the statically linked libgit2 are in NOTICE.
Not affiliated with Paris Hilton.