Securely store and use secrets in MCP clients without exposing them to models.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "secrets-mcp" yet — see the docs or source repo.
Use secrets-mcp to read an API key from the encrypted vault and run an authenticated command without exposing the key in the output.
Returns the command result while keeping the actual secret value hidden.
Use secrets-mcp to retrieve a stored access token, send a request to a protected HTTP endpoint, and show only the response.
Outputs the API response or status without revealing the raw token.
Fetch database credentials with secrets-mcp and render a configuration template while hiding sensitive values from the model.
Produces the rendered template or config while protecting secret fields from direct exposure.
Developers can use it in MCP clients to store and retrieve credentials for external services without exposing secret values to the model. This is useful for authenticated automation tasks.
DevOps or product teams can use the encrypted vault to authenticate commands and HTTP requests. The tool is designed to use sensitive material without revealing actual values to the model.
It is an encrypted credential vault for MCP clients that stores and uses sensitive material. It supports command execution, HTTP requests, and template rendering without exposing secret values to the model.
The provided description only confirms that it can store and use sensitive material such as credentials, keys, or tokens. For the exact supported scope, see the source repository.
The current materials do not provide installation steps, runtime requirements, or prerequisite setup. See the source repository for details.
Securely store and manage encrypted credentials for AI agents without hardcoded keys.
Let AI agents use secrets safely for server-side HTTP, shell, and SSH actions.
Securely lets AI agents access and manage secrets through MCP tools.
Securely store and retrieve local secrets for AI workflows without sending them to LLM APIs.
Securely manage secrets from keychains or encrypted files without chat exposure.
Create, encrypt, and manage SOPS secrets for development and operations workflows.