Docs menu+

What mcpvault is and how the docs are organised.

#mcpvault docs

mcpvault is a local, encrypted credential vault for AI agents. Store many accounts per service (Supabase, GitHub, Vercel, Stripe), point any MCP-compatible chat client at it once, then switch accounts mid-conversation by just asking.

These docs are also available as a single LLM-readable file at /llms.txt (index) and /llms-full.txt (every page concatenated). Paste either into your agent and it will know enough to walk you through the rest.

#Start here

  • Install: three commands, works on macOS, Windows, Linux.
  • Accounts: add, switch, rename, rotate tokens, remove. Multi-account workflows.
  • Backup & sync: back up the vault file, restore on a new machine, sync between machines.

#Reference

  • CLI reference: every mcpvault subcommand, flag, and environment variable.
  • Clients: which chat clients work, where the config file lives, what to paste.
  • Services: Supabase, GitHub, Vercel, Stripe token URLs, scopes, tools.
  • Security: how the vault is encrypted, where the key is cached, what the audit log records.
  • Troubleshooting: common errors and fixes.

#How it fits together

~/.mcpvault/
├── vault.enc        # AES-256-GCM ciphertext of every credential
├── active.json      # which label is currently active per service (no secrets)
└── vault.log        # append-only audit log (no secrets)

OS keyring
└── mcpvault.session # derived key, cached by your OS login (cleared on lock)

MCP servers
├── mcpvault server          # control plane: list / find / activate accounts
└── mcpvault wrap <service>  # one wrapper per service the agent talks to

#License

MIT. Source on GitHub.

Overview · mcpvault