KeyZula

com.keyzulaPublished by keyzula.comv1.2.4Updated Nov 5, 2026

Use passwords and API keys from your KeyZula vault without the assistant seeing them.

VerifiedSTDIODesktop onlyDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

KeyZula lets an AI assistant use passwords, API keys and tokens from your KeyZula vault via kz:// references, without the values entering the conversation.

What you can do
  • Check vault status and search items by name, username, website or folder, returning names and kz:// references but never values
  • Run commands with vault secrets placed in their environment variables, with values concealed in the output
  • Fill a template with secrets and write the result to a file only the user can read
  • Generate a strong random password or passphrase (not saved to the vault)
  • Optionally reveal a single value, such as a 2FA code, when explicitly enabled and approved by the user
When to use it
Useful when you want an assistant to deploy, run migrations or create .env files using real credentials while keeping the secret values out of the chat. It suits users who already keep their credentials in a KeyZula vault and want controlled, logged access from desktop AI clients.
Requirements
A free KeyZula account and the KeyZula command-line tool (npm @keyzula/cli or Homebrew), signed in and with the ssh-agent daemon unlocked. The server runs locally over stdio, typically via npx. Optionally set KEYZULA_SERVICE_TOKEN to limit access to an organization service account, or KEYZULA_MCP_ALLOW_REVEAL to offer read_secret. macOS, Linux and Windows are supported.
Before you install
The assistant can run programs and write files that contain your secrets, so enable confirmation (KEYZULA_MCP_CONFIRM) if you want approval before each use. read_secret is off by default and, when enabled via KEYZULA_MCP_ALLOW_REVEAL, still requires approval in a window on your computer. A service token (KEYZULA_SERVICE_TOKEN) is a credential and should be handled as a secret. Lock the vault with keyzula lock to cut off access.

Installation

In SourceWeft

  1. Open KeyZula in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

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.

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

ToolWhat it doesWhat the assistant receives
search_itemsSearches your vault by name, username, website or folderNames, locations, usernames, websites and kz:// references, never values
run_commandRuns a command with secrets in its environment variablesExit code and output, with secret values concealed
inject_templateFills a {{ kz://… }} template and writes a file only you can readOnly the file path
generate_passwordGenerates a strong password or passphraseThe generated value (not saved)
vault_statusShows whether KeyZula is signed in and unlockedStatus
read_secretShows one value, such as a 2FA codeOff by default; when turned on, every request needs your approval in a window on your computer

Requirements

  1. A KeyZula account (free).
  2. The KeyZula command-line tool, signed in and unlocked once in a terminal:
sh
npm i -g @keyzula/cli        # or: brew install keyzula/tap/keyzulakeyzula loginkeyzula 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):

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:

json
{  "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

SettingFlagEnvironment variable
Offer read_secret (every request still needs your approval)--allow-revealKEYZULA_MCP_ALLOW_REVEAL=true
Ask before every command or file that uses a secret--confirmKEYZULA_MCP_CONFIRM=true
Limit the assistant to an organization's service accountKEYZULA_SERVICE_TOKEN=kzsa_1_…

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: [email protected]

Source: README.md at commit 7008820

Tools

5

vault_status

Vault status

Shows whether KeyZula is logged in and the vault is unlocked.

Takes no parameters.

search_items

Search vault items

Searches the user's KeyZula vault by name, username, website or folder. Returns item names, locations, usernames, websites and the kz:// reference of each field. Secret values are never returned. Use the references with run_command or inject_template.

Parameterslimitquery

run_command

Run a command with secrets

Runs a program with secrets from the vault placed in its environment variables, without showing them to you. Give env values as kz:// references (plain strings are passed as they are). References look like "kz://<collection>/<item>/<field>" ("~" is the personal vault). Get them from search_items; never guess them. The command runs directly, not through a shell; for pipes or variable expansion use ["sh", "-c", "…"] and refer to the variable (e.g. "$DB_PASSWORD"). Secret values in the output are replaced with "<concealed by KeyZula>". Do not try to print or transform secrets to get around this.

Parameterscwdenvcommandrequiredtimeout_seconds

inject_template

Write a config file with secrets

Fills a template with secrets from the vault and writes the result to a file that only the user can read (mode 0600). Placeholders look like {{ kz://<collection>/<item>/<field> }}. References look like "kz://<collection>/<item>/<field>" ("~" is the personal vault). Get them from search_items; never guess them. The file's content is not returned to you; do not read the written file back.

Parameterstemplateoverwriteoutput_pathrequiredtemplate_path

generate_password

Generate a password

Generates a strong random password or passphrase. It is not saved to the vault.

Parameterskindwordslengthsymbols

Version history

2
  1. v1.2.4LatestNov 5, 2026
  2. v1.2.3Oct 29, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts
  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts