Repository navigation
v3.7.0 — Rename to vault-pkm + community marketplace install
Changed
- Plugin identity renamed from
obsidian-pkmtovault-pkm. The Claude Code plugin manifest, the MCP server registration, and the skill/command namespace (/vault-pkm:setup,/vault-pkm:pkm-write, etc.) all use the new name. MCP tools now appear undermcp__vault-pkm__vault_*. Rationale: the old name read as Obsidian-specific, but the server is a generic PKM layer that happens to follow Obsidian conventions. - Install from the official community marketplace. The documented install command is now:
The previous personal-marketplace install path is no longer documented, and
claude plugin marketplace add anthropics/claude-plugins-community claude plugin install vault-pkm@claude-community.claude-plugin/marketplace.jsonhas been removed. - Env var renamed to
VAULT_PKM_OPENAI_KEY(wasOBSIDIAN_PKM_OPENAI_KEY). A fallback chain keeps reading the old name andOPENAI_API_KEY, so existing configs continue to work; the doctor command prints a deprecation notice when only the old name is set.
Unchanged (deliberately)
- The npm package name stays
obsidian-pkm— the published version history andnpx obsidian-pkmbin are preserved. - The GitHub repo URL stays
AdrianV101/obsidian-pkm-plugin— the community marketplace entry pins installs to this repo, so renaming would break the install path.
Migration
Existing users installed from the personal marketplace:
- Uninstall the old plugin:
claude plugin uninstall obsidian-pkm@<your-current-marketplace>. - Install from the community marketplace (commands above).
- Rename your env var in
~/.claude/settings.jsonfromOBSIDIAN_PKM_OPENAI_KEYtoVAULT_PKM_OPENAI_KEY(old name still works, but is deprecated). - Permission entries (
mcp__plugin_vault-pkm_vault-pkm__*) will need re-granting on first tool use after the rename. - Vault data is untouched — the semantic index (
.obsidian/semantic-index.db) and activity log (.obsidian/activity-log.db) live inside$VAULT_PATH, not inside the plugin install.