Power your agent
คำสั่งของผู้เผยแพร่เอง ไม่ใช่เอนด์พอยต์ของ PlugMCP
Host a copy with our keys and logs.
npx -y @sarutobi-sasuke/[email protected]Claude Code ไม่มีลิงก์ติดตั้งสำหรับคำสั่งแบบโลคัล ให้คัดลอกคำสั่งด้านล่างแล้วรันในเทอร์มินัล
VAULT_MCP_PORT=<value> VAULT_MCP_GITHUB_OWNER=<value> VAULT_MCP_GITHUB_REPO=<value> VAULT_MCP_POLICY_FILE=<value> VAULT_MCP_TOKEN_FILE=<value> GITHUB_TOKEN=<secret> GITHUB_APP_ID=<value> GITHUB_APP_INSTALLATION_ID=<value> GITHUB_APP_PRIVATE_KEY_FILE=<secret> claude mcp add io.github.sarutobisasuke8-obsidian-github-mcp -- npx -y @sarutobi-sasuke/obsidian-github-mcp@0.1.0รันในเทอร์มินัล
{ "mcpServers": { "io.github.sarutobisasuke8-obsidian-github-mcp": { "command": "npx", "args": [ "-y", "@sarutobi-sasuke/[email protected]" ], "env": { "VAULT_MCP_PORT": "<value>", "VAULT_MCP_GITHUB_OWNER": "<value>", "VAULT_MCP_GITHUB_REPO": "<value>", "VAULT_MCP_POLICY_FILE": "<value>", "VAULT_MCP_TOKEN_FILE": "<value>", "GITHUB_TOKEN": "<secret>", "GITHUB_APP_ID": "<value>", "GITHUB_APP_INSTALLATION_ID": "<value>", "GITHUB_APP_PRIVATE_KEY_FILE": "<secret>" } } }}claude_desktop_config.json
URL แบบรีโมตหรือคำสั่งบนเครื่องของคุณ? การติดตั้งสองแบบต่างกันอย่างไร
รันบน PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
เปิดจากผู้เผยแพร่
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.
A permissioned MCP gateway for agent proposals to a Git-backed Obsidian vault.
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 handlingContents: 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
# Configure .env with your GitHub repository and token/app credentials before starting:
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:
- id: example-writer
name: Example Writer
role: bounded knowledge worker
disclosure_ceiling: internal
entry_reads: [README.md]
read: [Knowledge/**, Workspace/**]
write: [Workspace/Shared/**, Workspace/Example Writer/**]
deny: [Private/**, People/**, .obsidian/**]
git_brokers:
- broker: example-writer
branch: agent/example-writer
allow: [Workspace/Shared/**, Workspace/Example Writer/**]
never_versioned: [Private/**, People/**, .obsidian/**, secrets/**]
surface_rules:
- path: Workspace/Shared/**
required_frontmatter:
disclosure: public-safe
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.
A permissioned MCP gateway for agent proposals to a Git-backed Obsidian vault.
{ "mcpServers": { "io.github.sarutobisasuke8-obsidian-github-mcp": { "command": "npx", "args": [ "-y", "@sarutobi-sasuke/[email protected]" ], "env": { "VAULT_MCP_PORT": "<value>", "VAULT_MCP_GITHUB_OWNER": "<value>", "VAULT_MCP_GITHUB_REPO": "<value>", "VAULT_MCP_POLICY_FILE": "<value>", "VAULT_MCP_TOKEN_FILE": "<value>", "GITHUB_TOKEN": "<secret>", "GITHUB_APP_ID": "<value>", "GITHUB_APP_INSTALLATION_ID": "<value>", "GITHUB_APP_PRIVATE_KEY_FILE": "<secret>" } } }}เครื่องมือ
ยังไม่มีรายการเครื่องมือ เซิร์ฟเวอร์แบบรีโมตจะได้รายการหลังการตรวจสอบสถานะครั้งแรก
FAQ
คัดลอกคอนฟิก stdio สำหรับ Cursor, Claude Desktop, Claude Code หรือ VS Code ได้ในหน้านี้ คอนฟิกนี้ใช้การติดตั้งของผู้เผยแพร่ ไม่ใช่พร็อกซีของ PlugMCP
ผู้เผยแพร่ระบุตัวแปรสภาพแวดล้อมเหล่านี้: 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_FILE
Obsidian GitHub MCP ทำงานแบบโลคัลผ่าน stdio
ตรวจสอบล่าสุดเมื่อ 2026-11-09 A permissioned MCP gateway for agent proposals to a Git-backed Obsidian vault.
