Skip to content
mcp/harbor
Gemini CLI

vaultguard for Gemini CLI

io.github.ashishrao-4/vaultguard

AI agents use your Obsidian secrets by name — values never reach their context.

client:Gemini CLI transport:stdio runtime:npm

Install vaultguard in Gemini CLI

~/.gemini/settings.json · windows: %USERPROFILE%\.gemini\settings.json

Held in this page only — never stored, logged, or sent anywhere but back to your screen. 

{
  "mcpServers": {
    "vaultguard": {
      "command": "npx",
      "args": [
        "-y",
        "@ashishrao-4/vaultguard"
      ],
      "env": {
        "VAULTGUARD_PASSPHRASE": "<VAULTGUARD_PASSPHRASE>",
        "VAULTGUARD_VAULT_PATH": "<VAULTGUARD_VAULT_PATH>",
        "VAULTGUARD_HOME": "<VAULTGUARD_HOME>",
        "VAULTGUARD_ALLOW_GET_SECRET": "<VAULTGUARD_ALLOW_GET_SECRET>"
      }
    }
  }
}

Gemini expands $VAR and ${VAR} inside env values, so a secret can live in your shell rather than this file. Gemini CLI docs

vaultguard in other clients

vaultguard MCP server