Vaultguard MCP Server

Vaultguard is an MCP integration. AI agents use your Obsidian secrets by name — values never reach their context.

Packages and local setup

The published npm package is @ashishrao-4/vaultguard, version 0.1.2. Its declared MCP transport is stdio.

The package declares VAULTGUARD_PASSPHRASE (required): Passphrase that decrypts the encrypted secret blocks in your Obsidian vault.; VAULTGUARD_VAULT_PATH: Path to your Obsidian vault (overrides the one in ~/.vaultguard/config.json).; VAULTGUARD_HOME: Config directory (defaults to ~/.vaultguard).; VAULTGUARD_ALLOW_GET_SECRET: Set to 1 to enable get_secret (default: disabled so values never reach the agent)..

This package has launch arguments in its registry record. Use the maintainer’s configuration for those arguments rather than launching it with only the package name.

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 0.1.2 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related productivity & project management MCP servers for tools that cover the same kind of work.