Wrap local stdio MCP servers with pass-backed secret retrieval.
npx skills add https://github.com/cometjc/dev-skills --skill wrap-mcp
Please help me install this Agent Skill. Skill: wrap-mcp Source: https://github.com/cometjc/dev-skills/tree/main/skills/wrap-mcp Command: npx skills add https://github.com/cometjc/dev-skills --skill wrap-mcp
It prevents sensitive MCP credentials (tokens, API keys, passwords, client secrets) from being stored in MCP JSON/YAML configuration files by forcing all secrets to live in a secure secret store and only exposing them at runtime through a wrapper.
pass and fetch them on-demand for the MCP server process.command to a local wrapper script so the config never contains secret env vars, header values, or token arguments.pass without editing MCP configs, using a mcp-update-token workflow.Create a mcp-<server> wrapper that pulls the token from pass and update your Cursor/Claude/Hermes MCP configuration so its command points only to that wrapper.
High-intent search queries and answers about installing and using this skill.
To keep API keys out of MCP configuration files, use a wrapper script backed by the pass secret store. The wrapper fetches credentials at runtime so your JSON or YAML configs only reference the wrapper command, never the secrets themselves.
Pass-backed secret retrieval works by pointing the local stdio MCP server command to a wrapper that calls a helper like mcp-pass-show. The wrapper fetches tokens from pass on demand, ensuring secrets are never written into static config files.
Yes, the wrapper approach works with agent-facing MCP servers like Cursor, Claude, and Hermes. You update the MCP configuration so the command field points only to the local wrapper script, keeping credentials completely out of the config.
The best way to rotate tokens without editing configs is to update the stored credentials directly in pass. A mcp-update-token workflow fetches the new token on the next server run, eliminating the need to modify MCP JSON or YAML files.
GPG pinentry uses curses pinentry and gpg-agent caching to unlock interactively when needed. Decryption happens only when the wrapper fetches a secret, not during static config loading or chat sessions.
To prevent secrets from leaking, the wrapper and helper logic are designed to avoid exposing credentials through stdout, stderr, argv, process lists, tmux transcripts, or logs. Secrets are fetched and injected securely at runtime without leaving traces.
snqbStore and retrieve GPG-encrypted credentials using the pass CLI.
bobmatnycAutomates OAuth token refresh and management for Google Workspace MCP in Claude Code sessions.
ulpi-ioStore encrypted credentials and inject them into CLI tools and MCP servers.
pjmageeConfigure MongoDB MCP server authentication and environment variables.