0.2.1

Vault MCP Connector Obsidian Plugin 0.2.1

Public alpha release candidate for Obsidian Community Plugins.

Release Identity

• Community Plugin ID: vault-mcp-connector.
• Display name: Vault MCP Connector.
• This replaces the unpublished 0.2.0 candidate, whose vault-mcp ID was already reserved by another Community Plugin.
• Existing beta installs under .obsidian/plugins/vault-mcp/ are not upgraded in place. Disable and remove that candidate before installing 0.2.1.

What Is Included

• A persistent operational sidebar for access level, local server state, ChatGPT local access, index status, sync, and write proposals.
• A self-contained local MCP server compiled into main.js; packaged users do not need Node, npm, or a separate sidecar folder.
• One local file access selector: Off, scoped Read, scoped Read/write, or GOD read/write.
• Direct scoped and GOD writes with create, overwrite, exact edit, directory create, copy, move/rename, delete, and local audit support.
• Plugin-controlled indexing rules, manual approvals, redaction reporting, remote sync, multi-vault status, and hosted write-proposal review.
• Setup guidance for local clients, hosted ChatGPT access, and self-hosted Vercel deployments.

Safety Defaults

• Local filesystem access is Off by default.
• Hosted ChatGPT local access is disabled on every Obsidian startup and must be enabled for the current session.
• Scoped access enforces configured folders and operation permissions.
• GOD access is intentionally unrestricted and is labeled as such in the UI.
• Remote indexed-vault writes remain proposal-based; direct local writes do not create proposals or wait for Obsidian approval.
• The plugin does not include telemetry.

Verification

• Full local release gate: build, typecheck, tests, audits, MCP smokes, package checks, clean install, lifecycle, and OAuth checks.
• Real Obsidian acceptance uses only disposable vaults and the standard manifest.json, main.js, and styles.css release assets.
• Embedded local server startup with no external Node installation.
• GOD-mode direct create, write, exact edit, copy, move, and delete in disposable test locations, followed by cleanup and reset to Off.

Known Limitations

• Desktop only.
• Managed hosting onboarding is still alpha; local mode is the simplest no-cloud path for desktop MCP clients.
• Community directory availability depends on Obsidian review after submission.

0.2.0 (superseded candidate)

Superseded by 0.2.1. Do not install this candidate: its plugin ID, vault-mcp, was already reserved by another Obsidian Community Plugin. Install 0.2.1, which uses the unique vault-mcp-connector ID.

0.1.0

Vault MCP Obsidian Plugin 0.1.0

Private-alpha release for copied-vault, disposable-vault, and BRAT testing.

GitHub prerelease:

https://github.com/vault-mcp/platform/releases/tag/0.1.0

What Is Included

• Settings for server URL, sync token, vault id, index mode, write mode, include rules, exclude rules, manual allow rules, and write audit folder.
• Dashboard with safety boundary and configuration readiness checks.
• Connection preflight for server health, storage readiness, migration metadata, and configured-vault status before sync.
• Dry-run index preview for allowed, denied, review-required, and redacted notes.
• Review queue for sensitive notes held by policy.
• Sync of approved Markdown chunks to the configured Vault MCP server.
• Write proposal review for create, append, replace, frontmatter update, and rename operations.
• Local write apply for supported approved proposals after safety checks, with backup and audit notes.

Safety Defaults

• review_required is the default write mode.
• Exclude rules win before include and manual allow rules.
• The server stores a derived index and write proposals; it does not directly edit Obsidian files.
• Local write apply creates backup and audit notes under the configured audit folder.
• direct_apply remains experimental and should not be used for normal private-alpha testing.

Known Limitations

• Use copied or disposable vaults first. Do not point private-alpha testing at a live vault until the private-alpha safety review and release walkthrough gates pass.
• patch_note proposals are not accepted in this release.
• BRAT release assets are published on the 0.1.0 GitHub prerelease and can be verified with npm run plugin:brat:verify-github; copied-vault installed-file parity can be verified with npm run plugin:brat:verify-copy-install; the screenshot-backed BRAT UI walkthrough is still an external gate.
• Obsidian community-plugin submission is not enabled yet.
• Copied-vault Obsidian UI verification passed for create, append, replace, frontmatter, and rename proposals; a broader external-user walkthrough is still open.
• Public docs still need demo-vault data before wider release.

Verification Commands

npm run plugin:package
npm run plugin:verify-package
npm run plugin:brat:prepare
npm run plugin:brat:verify
npm run plugin:brat:verify-github
npm run plugin:brat:check-copy -- --check-github-release
npm run plugin:brat:verify-copy-install
npm run plugin:brat:prepare-ui-evidence
npm run plugin:brat:evidence-status
npm run plugin:brat:verify-ui-evidence
npm run plugin:smoke-fresh-install
npm run plugin:smoke-lifecycle
npm run build
npm run check:api
npm test

Upgrade Notes

This is the first private-alpha package. For later upgrades, preserve Obsidian's plugin data.json unless release notes explicitly say the settings shape changed.