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.

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.

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.

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.

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.