接入你的智能体
發布者自己的指令。不是 PlugMCP 端點。
用我們的金鑰與日誌託管一份副本。
npx -y [email protected]Claude Code 沒有本機指令的安裝連結。複製下方指令並在終端機中執行。
claude mcp add livesync-workers -- npx -y livesync-workers@0.12.0在終端機中執行。
{ "mcpServers": { "livesync-workers": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}claude_desktop_config.json
遠端 URL 還是本機指令？ 兩種安裝方式的差異
來自發布者
A Self-hosted LiveSync-compatible backend for Obsidian, with full-text and semantic search and an MCP server, running entirely on Cloudflare Workers.
Sync your vault from Obsidian the way you would to CouchDB, then let AI assistants (Claude, Cursor, Claude Code, …) read and search your notes through MCP.
Self-hosted LiveSync-compatible backend for Obsidian with search and MCP, for Cloudflare Workers
This is an independent project. It is not affiliated with the Self-hosted LiveSync plugin or its author. It implements the subset of the CouchDB API that the plugin uses, not CouchDB in general.
Built for Kuro. Available to everyone.
/livesync): the CouchDB-compatible API the plugin talks to. Your vault lives in a SQLite-backed Durable Object; no CouchDB server to run./mcp) with OAuth, exposing 11 tools:
listDirectory, listNotes, listRecentNotes, readNote, readDailyNote, searchNotes, grepNotes, vaultStatus (read),
appendToDailyNote, appendToNote (append), writeNote (write, with conflict detection)./ with your connection details.Notes written through MCP are regular LiveSync revisions, so they show up in Obsidian on the next sync.
会議室 finds it inside any word; ASCII text is matched by whole words, case- and width-insensitively.vaultStatus, past 50 million characters of text. Attachments do not count.grepNotes. Semantic search embeds the whole note in sections and is not affected.grepNotes query may use up to 32 index terms (a few words, or about 60 CJK characters).The server also sends MCP instructions telling assistants to read AGENTS.md at the vault root first, if it exists. Put your vault's layout and the rules you want agents to follow (where daily notes live, how to mark AI-written text, …) in that note and every connected assistant will see them before touching the vault.
LIVESYNC_PASSWORD: what the Obsidian plugin will log in with (the username is the LIVESYNC_USERNAME variable, obsidian by default).ADMIN_PASSWORD: for the admin login on the status page and when authorizing MCP clients.SESSION_SECRET: any long random string, e.g. openssl rand -hex 32.Later pushes to your copy of the repository redeploy automatically. Note that the copy is not a fork: it shares no history with this repository and does not receive updates by itself. To hear about new versions, Watch this repository → Custom → Releases. To upgrade, see docs/upgrading.md: it has a prompt you can hand to a coding assistant, and the git commands if you would rather run them yourself.
git clone https://github.com/odiak/livesync-workers.git
cd livesync-workers
npm install
npm run setup # creates the Vectorize index and R2 bucket
npx wrangler secret put LIVESYNC_PASSWORD
npx wrangler secret put ADMIN_PASSWORD
npx wrangler secret put SESSION_SECRET
npm run build && npm run deploy
build and deploy are separate scripts on purpose: Workers Builds runs build and then either deploy (production) or wrangler preview (preview builds).
The KV namespace for OAuth is provisioned automatically on the first deploy.
A Cloudflare account with Workers enabled. The Worker uses Durable Objects (SQLite), R2, KV, Vectorize and Workers AI; all have free tiers, but R2 needs a payment method on the account and usage beyond the free tiers is billed by Cloudflare. Embeddings are computed once per changed note.
In Self-hosted LiveSync's setup:
E2EE must stay off: the server has to read note contents to index them and serve them over MCP. The status page at / shows these values (sign in with the admin password to see the username).
Or skip the typing: after signing in on the status page, click Generate Setup URI. It produces an encrypted obsidian://setuplivesync?settings=… link plus a passphrase; choose Use Setup URI in the plugin's setup wizard and paste both. The URI is built in your browser (the server only supplies the connection details) and every click creates a new pair.
Point the client at https://<your-worker>.workers.dev/mcp (Streamable HTTP). It will open a browser window; sign in with ADMIN_PASSWORD and choose which scopes to grant:
New MCP OAuth connections have no expiry (access tokens still expire after one hour and are refreshed). Existing connections retain their original expiry until you reconnect.
Clients that cannot do OAuth can send Authorization: Bearer <MCP_STATIC_TOKEN> instead once you add that secret (wrangler secret put MCP_STATIC_TOKEN, or in the dashboard under Settings → Variables and Secrets). The token grants vault:read only; add vault:append and/or vault:write through the MCP_STATIC_TOKEN_SCOPES variable. Tools apply the same scope checks as for OAuth grants.
Variables (in wrangler.jsonc vars, editable in the dashboard; keep_vars is on, so variables added in the dashboard survive deploys):
The "not set" ones are optional and deliberately absent from wrangler.jsonc, because every vars entry becomes a required field in the Deploy form. Add them in the dashboard (Settings → Variables and Secrets) or to vars when you need them.
Secrets: LIVESYNC_PASSWORD, ADMIN_PASSWORD, SESSION_SECRET, and optionally MCP_STATIC_TOKEN (not in .dev.vars.example, since every entry there becomes a required field in the Deploy form). Empty values and change-me… placeholders count as unset; the status page tells you which ones are missing.
/livesync accepts the Obsidian app origins and this Worker’s origin. Other origins require an explicit host policy. HTTP Basic supports UTF-8 credentials; repeated failed sign-ins are throttled separately for LiveSync and the admin login. Daily notes: appendToDailyNote takes the date from the client; without one it falls back to today in UTC.
Obsidian ──LiveSync (CouchDB API)──▶ Worker ──▶ VaultDO (Durable Object, SQLite)
│ alarm: index changed notes
├──▶ Vectorize (Workers AI embeddings)
└──▶ R2 (full-text index segments)
MCP client ──OAuth──▶ Worker ──▶ VaultMCP (McpAgent) ──▶ vault client ──▶ VaultDO / Vectorize / R2
_changes feeds are waited on in the Worker over a hibernatable WebSocket, so the Durable Object sleeps between writes.The livesync-workers npm package (in packages/livesync-workers) is what this Worker is built on. A multi-tenant host implements VaultHost (credential verification and per-vault policy) and subclasses LiveSyncVaultDO; see docs/embedding.md.
npm install # also builds the library into packages/livesync-workers/dist (prepare)
npm run build # rebuild the library after editing packages/livesync-workers/src
npm test # library unit tests
npm run typecheck
npm run dev # wrangler dev (needs a Cloudflare login for AI/Vectorize)
See test/README.md for unit, workerd, official LiveSync CLI, actual Obsidian and reproducible benchmark commands.
Self-hosted LiveSync-compatible backend for Obsidian with search and MCP, for Cloudflare Workers
{ "mcpServers": { "livesync-workers": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}工具
尚無工具清單。遠端伺服器會在首次健康檢查後取得工具清單。
常見問題
在本頁複製適用於 Cursor、Claude Desktop、Claude Code 或 VS Code 的 stdio 設定。它使用發布者的安裝方式，而不是 PlugMCP 代理伺服器。
這筆記錄未列出必要的環境變數。
Livesync Workers 透過 stdio 在本機執行。
上次檢查時間：2026-11-15。 Self-hosted LiveSync-compatible backend for Obsidian with search and MCP, for Cloudflare Workers