sealkeep
Give AI agents the use of your secrets without the values: named secrets in the OS keyring, with Vault as a replica, injected into a command and redacted from its output. CLI + MCP + guard hook.
Install / Use
claude mcp add munhq -- npx -y github:munhq/sealkeepIf the server publishes to npm under a different name, use that package instead — check the repo README.
MCP Server
Model Context Protocol server
Quality Score
Category
SecuritySupported Platforms
Our assessment of sealkeep
sealkeep scores 74/100 on our quality scale, 1033rd of 1,108 Security skills we index.
Its MCP Server is 23 KB long, well organised into 16 sections with 19 code examples: a thorough specification that gives an agent plenty to work with.
It has 3 GitHub stars, so there is little community track record yet; judge it on its content.
Maintenance, license and trust
- The repository was last updated today, so sealkeep is actively maintained.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 92/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
sealkeep compared with similar skills
All 4 of these similar skills score higher than sealkeep; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| sealkeep (this skill)by munhq | 74 | 3 | today | MCP Server |
| Agent-Reachby Panniantong | 100 | 112.3k | 8d ago | CLAUDE.md |
| rufloby ruvnet | 100 | 81.9k | today | CLAUDE.md |
| headroomby headroomlabs-ai | 100 | 79.8k | today | CLAUDE.md |
| CowAgentby zhayujie | 100 | 48.0k | today | CLAUDE.md |
Frequently asked questions
- How do I install sealkeep?
- Run
claude mcp add munhq -- npx -y github:munhq/sealkeep. The install tabs above show the steps for each supported agent. - Which AI agents does sealkeep work with?
- It is written for Claude Code, Claude Desktop, Cursor and OpenAI Codex, as a MCP Server file. Other agents that read the same format can often use it too.
- Is sealkeep safe to use?
- It is MIT-licensed and scores 92/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is sealkeep still maintained?
- The repository was last updated today, so sealkeep is actively maintained.
Skill content
View source on GitHubsealkeep
sealkeep lets an AI agent use your secrets without seeing them.
You keep each secret one time, under a name such as shared/stripe/test/SECRET_KEY. The agent finds the name with sealkeep list, and runs a command with it. It never reads the value, and it never has to ask you for one.
The agent asks for a secret by its name. sealkeep puts the value into the environment of one command, runs the command, and replaces the value with [sealkeep:NAME] in all the output. The value does not go into the context, the transcript or a file.
agent ──► sealkeep run OPENROUTER_API_KEY -- sh -c 'curl -H "Authorization: Bearer $OPENROUTER_API_KEY" …'
│
├─ reads the value from a store ──► OS keyring (macOS Keychain, Secret Service, Windows Credential Manager)
│ └─► Vault KV v2 (a replica)
├─ starts the command with the value in its environment
└─ redacts the value from stdout and stderr ──► agent sees [sealkeep:OPENROUTER_API_KEY]
It has four parts:
- A CLI (
sealkeep):set,list,run,import,scan,sync, aliases and the store commands. - An MCP server (
sealkeep mcp): the toolslist_secrets,run_with_secretsandstore_status. No tool returns a value. - A guard hook (
sealkeep guard): it refuses the tool calls that would print a secret, for examplecat .env,sealkeep get,kubectl get secretorvault kv get. - A skill that tells the agent when and how to use the CLI.
Install
As an MCP server only (any client), the command is npx -y @munhq/sealkeep:
{ "mcpServers": { "sealkeep": { "command": "npx", "args": ["-y", "@munhq/sealkeep"] } } }
In Claude Code, the plugin adds the MCP server, the skill and the guard hook in one step:
/plugin marketplace add munhq/sealkeep
/plugin install sealkeep@sealkeep
The full install below does the same for Claude Code, Codex and Cursor.
Linux and macOS:
curl -fsSL https://raw.githubusercontent.com/munhq/sealkeep/main/install.sh | sh
The script downloads the binary of the newest release, checks it against SHA256SUMS, copies it to ~/.local/bin, and runs sealkeep install.
With Rust:
cargo install --locked --git https://github.com/munhq/sealkeep
sealkeep install
sealkeep install finds the AI clients on the machine. It adds the skill, the MCP server and the guard hook to each client:
| Client | Skill | MCP server | Guard hook |
|---|---|---|---|
| Claude Code (each config folder) | <config>/skills/sealkeep | claude mcp add --scope user | <config>/settings.json, PreToolUse on Bash, Read, Grep |
| Codex | $CODEX_HOME/skills/sealkeep | codex mcp add | $CODEX_HOME/hooks.json, PreToolUse (approve it one time with /hooks) |
| Cursor | ~/.cursor/skills/sealkeep | ~/.cursor/mcp.json | ~/.cursor/hooks.json, beforeShellExecution |
Options: --client claude,codex installs into the named clients only. --dry-run shows the plan. --no-skills, --no-mcp and --no-hooks leave out a part. Before sealkeep changes a JSON file, it writes a backup (<file>.bak-<unix time>). sealkeep uninstall removes what install added.
Run sealkeep doctor to check the stores and the clients.
Names
A name is <scope>/<project>/<env>/<KEY>:
| Part | Values | Example |
|---|---|---|
| scope | Who owns the secret: personal, the name of an employer or a client, or shared for one account that several scopes use | personal, acme, shared |
| project | The repository or the service | example-app, stripe, ovh |
| env | prod, dev, test, local. Leave it out when the secret has no environment (the API key of an account) | prod |
| KEY | The environment variable that the program reads | DATABASE_URL |
Folders are lower case (a-z, 0-9, ., _, -). The key is upper case (A-Z, 0-9, _) and is the variable that run sets.
personal/example-app/prod/DATABASE_URL
personal/example-app/dev/DATABASE_URL
personal/example-app/dev/STRIPE_SECRET_KEY -> shared/stripe/test/SECRET_KEY (alias)
acme/ovh/ovh-eu/APPLICATION_KEY
acme/cloudflare/API_TOKEN
shared/stripe/test/SECRET_KEY
shared/openrouter/API_KEY
One value, one name. When two projects use the same account, store the value one time under shared/…, and make an alias in each project folder. The project folder then has every variable that the project needs, and a rotation changes one value.
Store a secret
sealkeep set shared/openrouter/API_KEY -d "OpenRouter, the main account" # writes to every store
sealkeep asks for the value two times, with no echo. To pipe a value in, use --stdin:
some-password-tool show openrouter | sealkeep set shared/openrouter/API_KEY --stdin
To find the secrets on a machine, run scan. It prints the path of each .env file, its key names, a class for each key (secret, config or empty), and a group number for each value that is in more than one place. It never prints a value. It also lists other files that often hold a credential, by path only:
sealkeep scan ~/code --max-depth 4
To copy a file into a folder:
sealkeep import ../example-app/.env --to personal/example-app/dev \
--map STRIPE_SECRET_KEY=shar…[redacted]
sealkeep import ~/.ovh.conf --to acme/ovh # INI: one folder for each section
sealkeep set personal/github/PAT --from-file ~/.github-token
import reads dotenv files, and INI files (.ini, .conf, AWS credentials). It prints the names only. --map KEY=NAME stores the value at NAME and makes the project key an alias of it. If NAME already has a different value, import stops and says so. After the import, delete the source file, or keep it out of the reach of the agent.
Let the agent use it
Tell the agent what to do. The skill tells it to run sealkeep list for the names, and sealkeep run for the command:
sealkeep run shared/openrouter/API_KEY -- sh -c 'curl -sS -H "Authorization: Bearer $API_KEY" https://openrouter.ai/api/v1/key'
sealkeep run --all personal/example-app/dev -- npm run dev
sealkeep run -e GITHUB_TOKEN=pers…[redacted] -- gh api user
A name sets the variable named by its key. --all FOLDER sets one variable for each secret in the folder, the same as a .env file. --recursive also takes the subfolders; two secrets with the same key are then an error. -e VAR=NAME sets a variable with a different name. STORE:NAME reads from one store only.
For a tool that reads its secrets from a file, --dotenv writes a temporary file that only you can read. The file is in $XDG_RUNTIME_DIR/sealkeep when it exists. sealkeep puts the path where the command has {dotenv}, and it removes the file when the command ends. This example gives Playwright MCP the login of a test account. The agent types the name ADMIN_PASSWORD, and Playwright puts in the value:
sealkeep run --dotenv personal/example-app/dev/ADMIN_EMAIL --dotenv personal/example-app/dev/ADMIN_PASSWORD \
-- npx @playwright/mcp@latest --secrets {dotenv}
--secrets <path> is an option of @playwright/mcp (see its README).
See a value yourself
sealkeep get shared/openrouter/API_KEY
get works only when stdin and stdout are a terminal. An agent runs commands without a terminal, so get refuses, and the guard hook also refuses it.
Stores
sealkeep looks up a bare name in the stores in the order of the config file. The first store that has the name gives the value.
The config file is ~/.config/sealkeep/config.toml on Linux and ~/Library/Application Support/sealkeep/config.toml on macOS. $SEALKEEP_CONFIG sets another path. With no file, sealkeep has one keyring store named local.
[[store]]
name = "local"
kind = "keyring"
[[store]]
name = "vault"
kind = "vault"
address = "http://127.0.0.1:{port}"
mount = "agent"
auth = "kubernetes"
role = "sealkeep"
jwt_command = ["kubectl", "-n", "vault", "create", "token", "sealkeep", "--duration", "10m"]
port_forward = ["kubectl", "-n", "vault", "port-forward", "svc/vault", "{port}:8200"]
[aliases]
"personal/example-app/dev/STRIPE_SECRET_KEY" = "shar…[redacted]"
[guard]
block_dotenv = true
deny = ["example-secret-cli"]
The OS keyring
| OS | Store | |---|---| | macOS | the login Keychain | | Linux, BSD | the Secret Service (GNOME Keyring, KWallet) on the session D-Bus | | Windows | the Credential Manager |
Each secret is one entry with the service sealkeep and the secret name as the account. An index entry (__index__) keeps the names and the descriptions.
On Linux, the keyring must be unlocked. A desktop session unlocks it when you log in. A session with no desktop (SSH, a login with no keyring password) has a locked keyring, and no unlock prompt can show. Run this one time after each boot:
sealkeep unlock
It asks for the password of the login keyring and gives it to gnome-keyring-daemon --unlock. Each keyring call waits at most 30 seconds (SEALKEEP_KEYRING_TIMEOUT), so an agent gets an error, and the call does not hang.
A locked keyring does not stop a command. When one store does not answer, run and list
use the values of the other stores, and they print one warning for that store. A name that
only the locked store has fails on its own name, with the error of that store. A store that
you name with -s must answer.
Vault as a replica
A Vault (or OpenBao) KV v2 mount can hold a copy of the keyring, for a second machine or a backup. Each folder is one KV secret, and each key is one field of it: shared/stripe/test/SECRET_KEY is the field SECRET_KEY of agent/shared/stripe/test. The custom_metadata of each secret lists its keys and their descriptions, so list reads no value.
For a Vault inside Kubernetes, sealkeep can reach it through the Kubernetes API with a port forward, and log in with a short-lived ServiceAccount token. The machine then keeps no Vault token:
sealkeep store add-vault vault \
--address 'http://127.0.0.1:{port}' --mount agent --auth kubernetes --role sealkeep \
--jwt-command 'kubectl -n vault create token sealkeep --duration 10m' \
--port-forward 'kubectl -n vault port-forward svc/vault {port}:8200'
sealkeep sync --from local --to vault # one time, for the secrets that are already in the keyring
set, import and mv write to every store (a Vault store takes only names with a folder), so the stores stay the same. --store NAME writes to one sto
Truncated for display — read the full file on GitHub.
Related Skills
Agent-Reach
112.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
ruflo
81.9k🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
headroom
79.8kCompress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.
CowAgent
48.0kOpen-source personal AI assistant & Agent Harness. Plans tasks, runs tools and skills, self-evolves with memory and knowledge. Multi-agent, multi-model, multi-channel. Lightweight, extensible, one-line install.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
