LocalVault

Your secrets.
Your machine.

An encrypted home for API keys, tokens, and credentials. Give your tools access without copying secrets into AI chats or MCP configs.

Free, open source · CLI + local MCP · macOS & Linux

~/.localvault/vaults/workEncrypted

Your credentials, kept together.

myapp.DATABASE_URL••••••••••••
myapp.STRIPE_KEY••••••••••••
myapp.OPENAI_API_KEY••••••••••••
Unlock locally. Inject when needed.localvault exec --project myapp -- rails server
No account needed for local use.
Argon2id key derivationlibsodium encryptionProcess-scoped injectionReadable source code

A small tool.
A useful routine.

Explore the everyday commands. This demo shows illustrative output only: it never runs commands, reads your files, or asks for real secrets.

$ localvault init work
Create a passphrase for this local vault.

$ printf '%s' "$OPENAI_API_KEY" | localvault set myapp.OPENAI_API_KEY --stdin -v work
Secret stored in the encrypted vault.

$ localvault list -v work
myapp.OPENAI_API_KEY

Discover names. Keep values out of command arguments.
Illustrative replay · No real credentials · Nothing is executed

Keep the secret
out of the conversation.

LocalVault runs beside your tools. Your agent can discover a credential’s name and prepare an injection command without retrieving its value.

1 / Store

Encrypt on your machine

Use a local vault for credentials. Supply values through stdin rather than putting them in command arguments.

2 / Select

Give each process what it needs

Select keys, project groups, or mappings. Avoid exporting every credential into every command.

3 / Run

Inject into the child process

The command receives credentials through its environment. The agent does not need to paste their values into a tool call.

Start locally.

Install the CLI, create a vault, and connect your MCP client. Local use needs no cloud account or subscription.

With Homebrew

brew install inventlist/tap/localvault

Then create and unlock a vault:

localvault init localvault unlock localvault doctor

Without Homebrew

curl --proto '=https' --tlsv1.2 -fsSL https://inventlist.github.io/localvault/install.sh | sh

The installer uses an isolated Ruby gem prefix. Ruby 3.2+ and libsodium are required. Read the installer first.

Already use RubyGems? gem install localvault also works.

Connect your AI tool

localvault install-mcp claude-code localvault unlock localvault mcp --check

Cursor and Windsurf are also supported. Prefer list_secrets and localvault_build_exec for discovery and injection. Plaintext retrieval is an explicit, separate operation.

Understand the boundary.

Encryption helps only when the whole workflow respects it. Read the implementation, choose what you grant, and know where credentials can appear.

What local mode does

  • Stores encrypted vault files on your device.
  • Uses Argon2id and libsodium’s authenticated encryption.
  • Runs MCP locally over stdio.
  • Supports scoped process injection without requiring plaintext in model context.

What it cannot promise

  • A compromised device or untrusted child process can expose unlocked credentials.
  • A child process may print credentials into logs or output.
  • Explicit plaintext MCP retrieval puts the value into the calling client’s context.
  • Removing a recipient cannot erase credentials they already received.
Optional sync today. The current sync and team-sharing workflow uses InventList by default and uploads encrypted vault data. Local mode does not require it. User-owned remote storage and independently verified sharing are a proposed next step, not a shipped feature. Hosting this website on Kuickr does not change the vault’s storage behavior.

Read, then build.

Practical guides, the security model, and the source behind the commands.

A few practical questions.

Do I need an account?

No account is required to store and use secrets locally or run the local MCP server. The existing optional InventList sync workflow requires an account.

Is LocalVault free?

The CLI and local MCP are free and open source. A paid team service is a future possibility; it is not required for local use.

Does the website receive my secrets?

This site is documentation and a non-executing demo. It has no connection to your local vault and provides no secret-entry form. The optional sync service is separate and stores encrypted vault data today.

Can I share without trusting a hosted key directory?

The proposed design is to verify a recipient’s key through a separate trusted channel, encrypt locally, and exchange the encrypted files through storage you control. That workflow still needs implementation and review; the currently shipped team workflow uses InventList.