Keyfold

io.github.codewithkolinPublished by GitHub account codewithkolinv1.0.1Updated Oct 27, 2026

Use API keys from your Keyfold vault in commands and .env files. No tool returns a secret value.

VerifiedSTDIODesktop onlyDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Keyfold's MCP server lets an AI agent use API keys from a local encrypted vault without the model ever seeing the secret values.

What you can do
  • List project and key names from the vault
  • Write a .env file, run a command with keys injected, or import an existing .env file, each after approval in the app
  • Store a new key and create a project
  • No tool returns a secret value; every request waits for a click in the Keyfold app
When to use it
Useful when an agent needs to run commands or produce .env files that depend on API keys, and you want the keys kept in a local vault rather than pasted into the chat or config files.
Requirements
A Mac with the Keyfold app installed, running and unlocked; the keyfold CLI on PATH, installed from the app's Settings; the server is started as keyfold mcp over stdio. No account, cloud or telemetry is involved.
Before you install
A command you approve can still print a key, and the model reads what it prints; approvals can last one hour. The server can write .env files and run commands with keys injected, so review each request in the app. It needs the vault unlocked on the same machine.

Installation

In SourceWeft

  1. Open Keyfold 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

Keyfold core

The open-source parts of Keyfold, an offline-first vault for developers: API keys organised by project and environment, plus passwords, in one encrypted file. No account, no cloud, no telemetry.

The Keyfold app for Mac is built on these crates (Windows is coming through the Microsoft Store). Get it at keyfold.app/download; signed builds are also on the Releases page.

What is here

CrateWhat it does
crates/keyfold-coreArgon2id key derivation, XChaCha20-Poly1305 envelope encryption, the tamper-evident vault format, rolling backups, the Recovery Kit, .env parsing, key detection patterns, 2FA codes (RFC 6238) and offline Ed25519 licence verification
crates/keyfold-agentThe JSON-line protocol between the keyfold CLI and the running app, over an owner-only local socket
crates/keyfold-cliThe keyfold command line and the MCP server for Cursor and Claude Code. No tool returns a secret value; every request is approved in the app

Use it with an AI agent (MCP)

keyfold mcp lets Claude Code, Cursor, Codex, Gemini CLI and other MCP clients use your API keys without the model seeing them. Its seven tools list project and key names, write a .env file you approve, run a command with the keys injected, store a key, create a project and import a .env file. None of them returns a secret value. Every request waits for your click in the Keyfold app, which shows the command or file the keys are for.

  1. Install Keyfold for Mac. In the app, open Settings › General › Command line and MCP and click Install, which puts keyfold on your PATH.
  2. Add the server to your client:
claude mcp add --scope user keyfold -- keyfold mcp

Cursor (.cursor/mcp.json): { "mcpServers": { "keyfold": { "command": "keyfold", "args": ["mcp"] } } }

A command you approve can still print a key, and the model reads what it prints; the MCP guide covers that and one-hour approvals. The server needs the Keyfold app running and unlocked on the same Mac. The Dockerfile builds it on Linux only so that MCP directories can read its tool list.

MCP Registry name: mcp-name: io.github.codewithkolin/keyfold

Docs

  • Vault format: every byte of the file, and how it is authenticated.
  • Threat model: what Keyfold protects against, and what it cannot.
  • MCP and CLI guide: connecting an AI agent without showing it your keys.

Build and test

cargo test --workspacecargo clippy --workspace --all-targets -- -D warningscargo build --release -p keyfold-cli   # the `keyfold` binary

Rust stable, no other toolchain needed.

Security

Please report vulnerabilities privately; see SECURITY.md.

Licence

AGPL-3.0-only. See the LICENSE file in each crate. The Keyfold desktop app around these crates is proprietary.

Source: README.md at commit 42beb0f

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.1LatestOct 20, 2026

Score

50% 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

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • 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 listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts