Agent-Native Calendar
Agent-Native Google Calendar - manage events, sync, and public booking
Description from the maker (original English)
A permissioned MCP gateway for agent proposals to a Git-backed Obsidian vault.
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.
VAULT_MCP_PORT, VAULT_MCP_GITHUB_OWNER, VAULT_MCP_GITHUB_REPO, VAULT_MCP_POLICY_FILE, VAULT_MCP_TOKEN_FILE, GITHUB_TOKEN, GITHUB_APP_ID, GITHUB_APP_INSTALLATION_ID, GITHUB_APP_PRIVATE_KEY_FILEValues 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": {
"obsidian-github": {
"command": "npx",
"args": [
"-y",
"@sarutobi-sasuke/obsidian-github-mcp"
],
"env": {
"VAULT_MCP_PORT": "your-value",
"VAULT_MCP_GITHUB_OWNER": "your-value",
"VAULT_MCP_GITHUB_REPO": "your-value",
"VAULT_MCP_POLICY_FILE": "your-value",
"VAULT_MCP_TOKEN_FILE": "your-value",
"GITHUB_TOKEN": "your-value",
"GITHUB_APP_ID": "your-value",
"GITHUB_APP_INSTALLATION_ID": "your-value",
"GITHUB_APP_PRIVATE_KEY_FILE": "your-value"
}
}
}
}Run this in your terminal
claude mcp add obsidian-github --env VAULT_MCP_PORT=your-value --env VAULT_MCP_GITHUB_OWNER=your-value --env VAULT_MCP_GITHUB_REPO=your-value --env VAULT_MCP_POLICY_FILE=your-value --env VAULT_MCP_TOKEN_FILE=your-value --env GITHUB_TOKEN=your-value --env GITHUB_APP_ID=your-value --env GITHUB_APP_INSTALLATION_ID=your-value --env GITHUB_APP_PRIVATE_KEY_FILE=your-value -- npx -y @sarutobi-sasuke/obsidian-github-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"obsidian-github": {
"command": "npx",
"args": [
"-y",
"@sarutobi-sasuke/obsidian-github-mcp"
],
"env": {
"VAULT_MCP_PORT": "your-value",
"VAULT_MCP_GITHUB_OWNER": "your-value",
"VAULT_MCP_GITHUB_REPO": "your-value",
"VAULT_MCP_POLICY_FILE": "your-value",
"VAULT_MCP_TOKEN_FILE": "your-value",
"GITHUB_TOKEN": "your-value",
"GITHUB_APP_ID": "your-value",
"GITHUB_APP_INSTALLATION_ID": "your-value",
"GITHUB_APP_PRIVATE_KEY_FILE": "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": {
"obsidian-github": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@sarutobi-sasuke/obsidian-github-mcp"
],
"env": {
"VAULT_MCP_PORT": "your-value",
"VAULT_MCP_GITHUB_OWNER": "your-value",
"VAULT_MCP_GITHUB_REPO": "your-value",
"VAULT_MCP_POLICY_FILE": "your-value",
"VAULT_MCP_TOKEN_FILE": "your-value",
"GITHUB_TOKEN": "your-value",
"GITHUB_APP_ID": "your-value",
"GITHUB_APP_INSTALLATION_ID": "your-value",
"GITHUB_APP_PRIVATE_KEY_FILE": "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.
VAULT_MCP_PORT envGITHUB_APP_ID envGITHUB_APP_INSTALLATION_ID 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 SarutobiSasuke8, 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: VAULT_MCP_GITHUB_OWNER, VAULT_MCP_GITHUB_REPO, VAULT_MCP_POLICY_FILE, VAULT_MCP_TOKEN_FILE, GITHUB_TOKEN, GITHUB_APP_PRIVATE_KEY_FILE
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 (0.1.0) reached the registry 13 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.
A white-label Model Context Protocol server that gives selected AI agents bounded, auditable access to propose changes to an Obsidian vault stored in GitHub.
Each agent receives its own expiring MCP bearer token. The GitHub credential remains server-side. Read and write paths, denials, protected surfaces, proposal branches, and token revocation are controlled by operator-owned YAML files.
This is an independent open-source project. It is not affiliated with or endorsed by Obsidian or GitHub.
Giving an agent a general GitHub token is difficult to constrain and easy to misuse. This server creates a narrower boundary:
AI agent + individual MCP token
| v identity + fixed broker | v agent write scope AND broker publication scope | v deny, path, frontmatter, mutability, size, and secret checks | v server-side GitHub App token | v proposal branch for human review
The service has no tools for deleting files, merging branches, pushing to main or master, changing repository settings, editing workflows, or exposing credentials.
living, review-first, append-only, and immutable note handling| Tool | Purpose |
|---|---|
vault_whoami | Show the authenticated identity, broker, branch, and policy scopes. |
vault_list_allowed_paths | Explain effective read/write/deny boundaries. |
vault_explain_access | Dry run a single path. Report whether read, list, or write would be permitted and which policy rule decides it. No GitHub call. |
vault_list_files | List an authorised directory while filtering denied children. |
vault_read_file | Read an authorised UTF-8 vault file. |
vault_create_file | Create a file on the identity's fixed proposal branch. |
vault_update_file | Update a permitted file while respecting mutability. |
vault_append_file | Append while preserving all existing bytes. |
Contents: read and write, or a fine-grained PAT for local testingInstall from source (the current supported path):
git clone https://github.com/YOUR_ACCOUNT/obsidian-github-mcp.git
cd obsidian-github-mcp npm ci cp .env.example .env cp config/policy.example.yaml config/policy.yaml cp config/tokens.example.yaml config/tokens.yaml npm run token:new npm run check
npm start
Configure .env (specifying your repository and either a GITHUB_TOKEN or GitHub App credentials), replace the sample policy, and put only the generated token's SHA-256 in config/tokens.yaml. Give the raw bearer token to exactly one MCP client.
To verify a checkout before configuring a running service:
npm ci
npm run check npm run test:e2e
These checks use synthetic notes, mock GitHub responses and loopback transports. They need no GitHub or MCP credentials. Note regressions cover Unicode/path encoding, CRLF frontmatter, malformed metadata, UTF-8 size limits and append-only byte preservation. CI runs the same checks on Linux and Windows with Node.js 22 and 24. The 8 tools listed above are the current server surface; tests do not publish proposals to a real vault.
Once v0.1.0 is published to npm, a global install will also be available:
# Available once v0.1.0 is published (not yet on the npm registry).
npm install -g @sarutobi-sasuke/obsidian-github-mcp
The default endpoints are:
GET http://127.0.0.1:3210/healthz
POST http://127.0.0.1:3210/mcp
MCP clients must send:
Authorization: Bearer vault_<generated-token>
The effective write scope is the intersection of the agent grant and its broker:
policy_version: 1
authority: operator-only
agents:
git_brokers:
never_versioned: [Private/, People/, .obsidian/, secrets/]
surface_rules:
An auth binding then maps one token hash to that identity and broker. The binding cannot grant paths that the policy does not grant.
See Permissions documentation for provisioning and revocation.
Production deployments should use a GitHub App installed only on the vault repository. Configure:
GITHUB_APP_ID=123456
GITHUB_APP_INSTALLATION_ID=12345678 GITHUB_APP_PRIVATE_KEY_FILE=/run/secrets/vault-mcp.pem
The server creates short-lived installation tokens restricted again to the configured repository and contents: write. A repository-scoped GITHUB_TOKEN is supported as a local-development fallback.
The included container runs as a non-root user with a read-only root filesystem. Put TLS, a private overlay network, or an authenticated gateway in front of the service before making it remotely reachable.
See Deployment guide.
npm run check
npm audit --audit-level=high
Tests cover policy parsing, write-scope intersection, deny precedence, traversal attempts, frontmatter rules, mutability, secret detection, token bindings, and fixed-branch GitHub writes.
Run npm run test:e2e for a clean tarball installation and real MCP HTTP client proof against a test-only GitHub substitute. It exercises proposal writes, denied paths/content, immutable and append-only notes, stale-write conflicts, invalid policy reloads, live token revocation and content-free audit records. CI runs this proof on Windows/Linux with Node 22/24, and the release workflow requires it.
Policy and token files reject unknown keys. Only policy_version: 1 and authority: operator-only are supported. Correct misspelt fields or remove unsupported metadata before upgrading; silently ignored restrictions are no longer accepted. Release evidence and remaining gates.
The draft MCP Registry npm entry describes a self-hosted Streamable HTTP process, not a stdio server. A compatible client starts the process with the declared environment and connects to http://127.0.0.1:{VAULT_MCP_PORT}/mcp (port 3210 by default). Supply the existing policy and token-file paths plus the repository owner/name. For GitHub access, use either GITHUB_TOKEN or all three documented GitHub App variables. The manifest cannot express that alternative group; runtime configuration validates it. The process does not create credentials, provision a hosted endpoint or bypass its existing bearer-token checks. The namespace preserves the exact GitHub owner spelling. prepublishOnly includes the registry/package gate; no login or publication is performed by it.
Read Security policy before deployment. Report suspected vulnerabilities privately rather than opening a public issue with exploit details.
Apache-2.0. See Apache-2.0 License.