PKV Sync

● Active

io.github.CyberKurry/pkv-sync

Self-hosted, Git-native Obsidian vault sync with a built-in MCP server, search, and wiki lint.

Connect this server

One click to install, or copy the config below. Suits: Claude Desktop · Cursor.

Add to Cursor Add to VS CodeClaude Desktop / Claude Code: paste the config below.

Or add it manually — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor):

{
  "mcpServers": {
    "pkv-sync": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-v",
        "{data_dir}:/var/lib/pkv-sync",
        "-v",
        "{config_file}:/etc/pkv-sync/config.toml:ro",
        "ghcr.io/cyberkurry/pkv-sync:1.10.2",
        "-c",
        "/etc/pkv-sync/config.toml",
        "mcp"
      ],
      "env": {
        "PKV_TOKEN": "<your PKV_TOKEN>",
        "PKV_VAULT_ID": "<your PKV_VAULT_ID>"
      }
    }
  }
}
One line, from the terminal
Claude Code
claude mcp add --env PKV_TOKEN='<your PKV_TOKEN>' --env PKV_VAULT_ID='<your PKV_VAULT_ID>' --transport stdio pkv-sync -- docker run -i --rm -v '{data_dir}:/var/lib/pkv-sync' -v '{config_file}:/etc/pkv-sync/config.toml:ro' ghcr.io/cyberkurry/pkv-sync:1.10.2 -c /etc/pkv-sync/config.toml mcp
OpenAI Codex CLI
codex mcp add pkv-sync --env PKV_TOKEN='<your PKV_TOKEN>' --env PKV_VAULT_ID='<your PKV_VAULT_ID>' -- docker run -i --rm -v '{data_dir}:/var/lib/pkv-sync' -v '{config_file}:/etc/pkv-sync/config.toml:ro' ghcr.io/cyberkurry/pkv-sync:1.10.2 -c /etc/pkv-sync/config.toml mcp
VS Code
code --add-mcp '{"name":"pkv-sync","type":"stdio","command":"docker","args":["run","-i","--rm","-v","{data_dir}:/var/lib/pkv-sync","-v","{config_file}:/etc/pkv-sync/config.toml:ro","ghcr.io/cyberkurry/pkv-sync:1.10.2","-c","/etc/pkv-sync/config.toml","mcp"],"env":{"PKV_TOKEN":"<your PKV_TOKEN>","PKV_VAULT_ID":"<your PKV_VAULT_ID>"}}'

Syntax from each client's docs (Claude Code: claude mcp add; Codex: codex mcp add; VS Code: code --add-mcp). Placeholders in angle brackets are values you fill in.

Environment variables
  • PKV_TOKENrequiredsecretA PKV Sync device token with access to the vault this session should expose
  • PKV_VAULT_IDrequiredVault id the MCP session exposes (the vault is listed in the admin panel)

A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.

Category
Productivity
Version
1.10.2
Registry
active
Published
11/19/2026
Listed in:Official MCP registry ↗how this is checked

Is it safe? Is it maintained?

Serverdex check: Nov 22, 2026

Looks healthy: PKV Sync is maintained, open source.

Maintained
Active
Last commit 2 days ago (Nov 19, 2026), 0 open issues.
Official registry
Active
Published as io.github.CyberKurry/pkv-sync in the official MCP registry, version 1.10.2.
Source
Open source, AGPL-3.0
Public repository under the AGPL-3.0 licence, 11 stars, 1 forks.
Runs
On your machine
A local Docker package started by your client; it can reach whatever your user account can.
Credentials
2 required
Declared environment variables: PKV_TOKEN, PKV_VAULT_ID. They stay on your machine; the config on this page shows where each goes.
Owner
Unclaimed
Nobody has claimed this page yet; the data above comes from the registry, GitHub and the live check.

Facts only: last commit and licence from GitHub, the entry's status from the official registry, credentials from the live check. Not a code audit — run the security scan on the endpoint yourself.

On GitHub

read Nov 21, 2026
Stars
11
Forks
1
Last push
Nov 19, 2026
License
AGPL-3.0

Rustgitobsidianrustself-hostedsqlitesync

From the README

PKV Sync PKV Sync is a self-hosted, Git-native sync server for Obsidian vaults. The name is PKV Sync: PKV is the initialism of Personal Knowledge Vault, and Sync is spelled out in full. Document version: v1.10.2. English · 简体中文 · 繁體中文 · 日本語 · 한국어 Status PKV Sync 1.10.2 ships its MCP Registry metadata under the canonical GitHub namespace case (io.github.CyberKurry/pkv-sync), which is the name the registry's OCI ownership check compares against. The product content matches 1.10.1: an edit made while a pull is downloading a file becomes a visible conflict instead of being pushed over the other device's committed version; a file the server refuses is reported on every pass instead of turning the status bar green, and one per-file rejection no longer wedges the rest of the vault; moving a note with a non-ASCII name keeps its Markdown links intact; and an interrupted self-update restores the previous plugin build. Upgrade the server and plugin together. Features Sync • Multi-user, multi-vault sync over authenticated devices, with per-vault push locks and idempotent retries. • Real-time push. Small edits land sub-second over Server-Sent Events; polling stays as a safety net. • Git is the source of truth. Every vault is a bare git repo, so per-file history, unified diff, and single-file restore work out of the box — in the plugin and in the admin panel. • Conflict-safe.…

Read the full README on GitHub →

The most-starred Productivity servers in the index, with their live-check result.

ServerStarsLast pushLive check
Front-End Checklist74,746Oct 2026Working
Windmill18,600Nov 2026Needs sign-in
Agent-Native Content7,735Nov 2026Needs sign-in
Agent-Native Calendar7,735Nov 2026Needs sign-in
Agent-Native Plan7,735Nov 2026Needs sign-in

PKV Sync: questions people ask

Is PKV Sync a remote or a local MCP server?
According to its entry in the official MCP registry, PKV Sync ships as a local package (Docker) that your client starts on your machine.
Does PKV Sync need an API key?
Its registry entry declares 2 required environment variables: PKV_TOKEN, PKV_VAULT_ID. The config on this page shows where each goes.
Is PKV Sync safe to use?
Looks healthy: PKV Sync is maintained, open source. In detail — maintained: Active; official registry: Active; source: Open source, AGPL-3.0; runs: On your machine; credentials: 2 required. Serverdex check of Nov 22, 2026. This is a reading of the repository, the registry entry and the live check, not a code audit; run the Serverdex security scan on the endpoint before trusting it with real data.
Is PKV Sync still maintained?
Active: the repository's last commit 2 days ago. Last push Nov 19, 2026, 11 GitHub stars, AGPL-3.0 licence. Read from GitHub on Nov 21, 2026.
How do I add PKV Sync to Claude, Cursor or VS Code?
Copy the config in "Connect this server" into your client's MCP config file (claude_desktop_config.json, ~/.cursor/mcp.json or .vscode/mcp.json), or use the one-click Add to Cursor / Add to VS Code buttons and the one-line commands for Claude Code and Codex; then restart the client.
Browse all Productivity →

Add the badge to your site

Show visitors that PKV Sync is listed here — it’s also the link we check for a free listing.

PKV Sync — listed on Serverdex

HTML — for your website

<a href="https://serverdex.io/server/io-github-cyberkurry-pkv-sync?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="PKV Sync — listed on Serverdex" width="123" height="40" loading="lazy"></a>

Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.

Markdown — for your README

[![PKV Sync — listed on Serverdex](https://serverdex.io/brand/badge.svg)](https://serverdex.io/server/io-github-cyberkurry-pkv-sync?utm_source=badge)

Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.

Add to CursorAdd to VS CodeOpen in Claude Code

Install buttons — for your README

[![Add to Cursor](https://serverdex.io/brand/install-cursor.svg)](https://serverdex.io/install/cursor/io-github-cyberkurry-pkv-sync) [![Add to VS Code](https://serverdex.io/brand/install-vscode.svg)](https://serverdex.io/install/vscode/io-github-cyberkurry-pkv-sync) [![Open in Claude Code](https://serverdex.io/brand/install-claude-code.svg)](https://serverdex.io/install/claude-code/io-github-cyberkurry-pkv-sync)

One click opens Cursor or VS Code with this server's config prefilled; the Claude Code button lands on the one-line command. The links point at Serverdex, so when your config changes the buttons keep working.

Install buttons — HTML for your docs

<a href="https://serverdex.io/install/cursor/io-github-cyberkurry-pkv-sync"><img src="https://serverdex.io/brand/install-cursor.svg" alt="Add to Cursor — via Serverdex" width="140" height="28"></a>
<a href="https://serverdex.io/install/vscode/io-github-cyberkurry-pkv-sync"><img src="https://serverdex.io/brand/install-vscode.svg" alt="Add to VS Code — via Serverdex" width="147" height="28"></a>
<a href="https://serverdex.io/install/claude-code/io-github-cyberkurry-pkv-sync"><img src="https://serverdex.io/brand/install-claude-code.svg" alt="Open in Claude Code — via Serverdex" width="180" height="28"></a>

Same buttons as plain links for a docs page or website.

Prefer a live badge with the score, stars and live check? Score badge (links to a page that explains the number and back to this listing).