Allows AI assistants to write .env files with secrets from a local database without exposing secret values, providing tools to search for secrets by name/description and write them directly to .env files
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Secret MCPadd my OpenAI API key to the project's .env file"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Secret MCP
A desktop app for managing secrets with an MCP server that lets AI coding assistants write .env files without ever seeing the secret values.
Why?
Generating .env file is a pain, especially because there is no vibing out of it. But its an even stronger pain to leak secrets to AI coding assistants run on the cloud.
Features
Desktop App: Simple window for managing secrets (name, description, value)
MCP Server: Two tools for AI assistants:
search_secrets: Find secrets by name/description (never exposes values)write_env: Write secrets to.envfiles (values go straight to file, never to AI)
Local Storage: All secrets stored locally in SQLite
npm Package: Just
npx secret-mcp- no build required
Installation
Desktop App
Download from Releases or build from source:
npm install
npm run tauri buildMCP Server Setup
Add to your MCP client config:
"secret-mcp": {
"command": "npx",
"args": ["secret-mcp"]
}Usage
Open Secret MCP app
Add your secrets (API keys, tokens, etc.)
When coding with AI, it will automatically use
search_secretsandwrite_envto set up your.envfiles (Note: the name of the secret is the variable name in the.envfile)
MCP Tools
search_secrets
Search for secrets by name or description. Returns names and descriptions only - values are never exposed.
// Input
{ query: "openai" }
// Output
[
{ name: "OPENAI_API_KEY", description: "OpenAI API key" }
]write_env
Write secrets to a .env file. Values go directly from your local database to the file - never passed through the AI.
// Input
{
keys: ["OPENAI_API_KEY", "DATABASE_URL"],
path: "/Users/you/project/.env"
}
// Output
"Successfully wrote 2 secret(s) to /Users/you/project/.env"Data Storage
Secrets are stored locally:
macOS:
~/Library/Application Support/secret-mcp/secrets.dbLinux:
~/.local/share/secret-mcp/secrets.dbWindows:
%APPDATA%/secret-mcp/secrets.db
Security
Secret values never leave your machine (except to
.envfiles you specify)MCP server only returns secret names and descriptions to the AI
.envfiles written with600permissions (owner read/write only)
Tech Stack
Desktop: Tauri 2.0 + Svelte 5 + TypeScript
MCP Server: Node.js + @modelcontextprotocol/sdk + better-sqlite3
License
MIT