KeyZula

KeyZula MCP server

Let GitHub Copilot, Claude, Cursor and other AI assistants use the passwords, API keys and tokens in your KeyZula vault without the values ever entering the conversation.

The assistant finds items by name, website or username and passes secrets to the programs it runs through kz:// references. Values go into the environment of a command (concealed in its output) or into a file only you can read. The assistant receives names and references, never the secrets themselves.

• MCP Registry: com.keyzula/keyzula
• Package: @keyzula/cli on npm (keyzula mcp, stdio)
• Website and setup guide: keyzula.com/en/ai

This repository holds the documentation and registry metadata for the server. The server is part of the KeyZula command-line tool, published on npm and Homebrew.

Tools

Requirements

1. A KeyZula account (free).
2. The KeyZula command-line tool, signed in and unlocked once in a terminal:

npm i -g @keyzula/cli        # or: brew install keyzula/tap/keyzula

keyzula login keyzula ssh-agent --daemon

The MCP server reads only from this unlocked agent and never asks for your master password. It runs on macOS, Linux and Windows.

Configuration

VS Code and GitHub Copilot

Install from the MCP server gallery in VS Code, or add it to .vscode/mcp.json (or your user mcp.json):

{

"servers": { "keyzula": { "type": "stdio", "command": "npx", "args": ["-y", "@keyzula/cli", "mcp"] } } }

If you installed the CLI globally, you can use "command": "keyzula", "args": ["mcp"] instead. Desktop apps may not see your terminal's PATH; use the full path from which keyzula (Windows: where keyzula) if needed.

Claude, Cursor, Windsurf and other clients

Most clients use the mcpServers format:

{

"mcpServers": { "keyzula": { "command": "npx", "args": ["-y", "@keyzula/cli", "mcp"] } } }

Claude Code: claude mcp add keyzula -- npx -y @keyzula/cli mcp. For Claude Desktop, a one-click extension is available at keyzula.com/en/ai.

Options

Usage

Ask in plain language; the assistant picks the right item and tool:

• "Deploy with the Cloudflare API token from KeyZula."
• "Run the database migrations using the staging Postgres password."
• "Create a .env file for this project from my KeyZula items."
• "Which KeyZula items do I have for AWS?"

For example, run_command can run wrangler deploy with CLOUDFLARE_API_TOKEN set to kz://~/Cloudflare/password (~ is your personal vault). The command gets the value; the assistant sees only the reference and the command's output, with the value concealed.

Privacy and control

• Vault data is end-to-end encrypted; the server never sees it in plain text. The MCP server talks to the KeyZula agent on your computer over a private local socket.
• Every use appears in your access log as "Used by an AI assistant" (item, action and time, never the value).
• Lock the vault at any time with keyzula lock; the assistant then has no access until you unlock it.
• Nothing is sent to the AI provider or any third party by the server itself.

More: keyzula.com/en/ai · Command-line guide · Privacy policy · Support: info@keyzula.com