Works with AI

Let your assistant use your passwords, not see them.

KeyZula's MCP server connects Claude, Cursor, GitHub Copilot and other AI assistants to your vault. The assistant connects to databases, deploys and writes config files, while passwords and API keys never enter the chat.

Set it up Command line guide

YouHow many users are in the production database?

keyzula · search_items"postgres"

kz://Production/Postgres/password

keyzula · run_commandpsql -c "select count(*) from users"

PGPASSWORD=<concealed by KeyZula>
count
-------
1284

AssistantThere are 1,284 users in the production database. I connected without seeing the password.

Works with assistants that support MCP

Claude
GitHub Copilot
Cursor
Gemini
VS Code
OpenAI Codex
Windsurf
JetBrains
Zed
Cline

Works with any client that can start local (stdio) MCP servers. Trademarks belong to their owners.

Ready in three steps

Setup takes a few minutes; after that you tell your assistant what you need in plain language.

Install the command-line tool

With Homebrew on macOS and Linux, or as a single file on Windows. Sign in and unlock your vault once.

Add it to your assistant

One command or a few lines of configuration for Claude, Cursor, VS Code and others.

Ask

Say "deploy to staging" or "create the .env file with the API key". The assistant finds the right item and uses the secret without seeing it.

Security first

Secrets never enter the chat

Neither the AI provider nor the assistant sees your passwords. The key to your vault stays with you.

The assistant doesn't see values

Search results contain only names, usernames, websites and kz:// references. Values go into a command's environment or a file only you can read, and are concealed in the output.

Seeing a value needs your approval

The tool that shows a password or 2FA code is off by default. If you turn it on, every request asks for your approval in a KeyZula window on your computer that the assistant can't click.

Never asks for your master password

The MCP server reads only from the agent you unlocked. If it's locked, the assistant asks you to unlock it; your password is never sent anywhere.

Every use is logged

Each item the assistant uses shows up in the access log as "Used by an AI assistant". For teams, a service account opens only the collections you choose.

Tools the assistant can use

Each tool states what it returns. The only tool that returns a value doesn't run without your approval.

Tool	What it does	Returned to the assistant
search_items	Searches your vault by name, username, website and folder	Names, locations, usernames, websites and kz:// references
run_command	Runs a command with secrets in its environment variables	Exit code and output with values concealed
inject_template	Fills a {{ kz://… }} template and writes a file only you can read	Only the file path
generate_password	Generates a strong password or passphrase	The generated value (not saved)
vault_status	Shows sign-in and lock status	Status
read_secret	Shows a field's value (password, 2FA code…)	The value, only with --allow-reveal and your approval each time

Setup

Install the command-line tool and sign in first, then pick your assistant.

Preparation (once)

macOS · Linux

brew install keyzula/tap/keyzula
keyzula login
keyzula ssh-agent --daemon

Windows (PowerShell)

$dir = "$env:LOCALAPPDATA\Programs\KeyZula"
Invoke-WebRequest https://github.com/KeyZula/homebrew-tap/releases/download/v1.2.1/keyzula-1.2.1-windows-x64.zip -OutFile "$env:TEMP\keyzula.zip"
Expand-Archive -Force "$env:TEMP\keyzula.zip" $dir
[Environment]::SetEnvironmentVariable("Path", [Environment]::GetEnvironmentVariable("Path", "User") + ";$dir", "User")
# Yeni bir terminal açın / open a new terminal:
keyzula login
keyzula ssh-agent --daemon

Desktop apps may not see your terminal's PATH, so the examples use the full path. Find yours with which keyzula (on Windows, where keyzula). On Intel Macs it's /usr/local/bin/keyzula.

With Node.js (including Windows) you can also install it with npm i -g @keyzula/cli. To use it without installing, set the command to npx and the arguments to ["-y", "@keyzula/cli", "mcp"].

Claude Code

One command in the terminal. With --scope user it's available in all your projects.

claude mcp add --scope user keyzula -- keyzula mcp

Claude Desktop

Download the Claude Desktop extension (.mcpb)

Easiest: download the KeyZula extension and double-click it; Claude Desktop installs it. In its settings you can turn on showing values and approval for every use. You still need the preparation above (sign-in and ssh-agent). To set it up by hand:

Open claude_desktop_config.json with Settings → Developer → Edit Config, add this and restart Claude.

{
  "mcpServers": {
    "keyzula": { "command": "/opt/homebrew/bin/keyzula", "args": ["mcp"] }
  }
}

Cursor

Add it to ~/.cursor/mcp.json (or .cursor/mcp.json in a project).

{
  "mcpServers": {
    "keyzula": { "command": "/opt/homebrew/bin/keyzula", "args": ["mcp"] }
  }
}

VS Code · GitHub Copilot

Add it to .vscode/mcp.json in your project; the tools appear in GitHub Copilot's agent mode.

{
  "servers": {
    "keyzula": { "type": "stdio", "command": "/opt/homebrew/bin/keyzula", "args": ["mcp"] }
  }
}

Windsurf

Add it to ~/.codeium/windsurf/mcp_config.json.

{
  "mcpServers": {
    "keyzula": { "command": "/opt/homebrew/bin/keyzula", "args": ["mcp"] }
  }
}

Gemini CLI

Add it to the mcpServers section of ~/.gemini/settings.json.

{
  "mcpServers": {
    "keyzula": { "command": "/opt/homebrew/bin/keyzula", "args": ["mcp"] }
  }
}

OpenAI Codex

One command in the terminal; the server is saved to ~/.codex/config.toml.

codex mcp add keyzula -- keyzula mcp

JetBrains AI Assistant

In Settings → Tools → AI Assistant → Model Context Protocol (MCP), add a new server and paste this configuration.

{
  "mcpServers": {
    "keyzula": { "command": "/opt/homebrew/bin/keyzula", "args": ["mcp"] }
  }
}

In other MCP clients (Zed, Cline and more), use keyzula as the command and mcp as the argument.

Frequently asked questions

Does the AI provider see my passwords?

No. The assistant only sees item names, usernames, websites and kz:// references. Values go into the environment of a command running on your computer or into a file with 0600 permissions, and are concealed in the command's output. The tool that shows a value is off by default, and when it's on every request waits for your approval.

Which assistants does it work with?

Any client that can start local (stdio) MCP servers: Claude Desktop, Claude Code, Cursor, VS Code and GitHub Copilot, Windsurf, Gemini CLI, OpenAI Codex, JetBrains AI Assistant, Zed, Cline and others. Web apps that can only connect to remote MCP servers over the internet aren't supported yet.

Could the assistant reveal a password through a command it runs?

KeyZula conceals the values and their common encodings (base64, URL encoding) in the output, but a command can transform a value however it likes. Keep your assistant's approval of commands on, or start KeyZula with --confirm to approve every use.

How do we use it as a team?

Create a service account, select only the collections the assistant needs and start the MCP server with KEYZULA_SERVICE_TOKEN. The assistant sees only those collections, every read is written to your organization's audit log and the token can be revoked with one click.

Does it cost anything?

No. The MCP server is part of the command-line tool and, like everything in KeyZula, free.

Secure your keys today.

Create an account in seconds. Completely free, no credit card required.

Get Started Free