Secure permission layer between AI agents and your .env files
MCP server for envibe - the missing permission layer between AI agents and your .env.
Add to your AI tool's MCP config:
{
"mcpServers": {
"envibe": {
"command": "npx",
"args": ["envibe-mcp"]
}
}
}
claude mcp add envibe npx envibe-mcp
Add to claude_desktop_config.json:
~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonAdd to your editor's MCP settings (see main envibe docs for details).
On first run, envibe automatically:
.env.manifest.yaml from your .env.example.env.ai (filtered view for AI).env file accessThis is the MCP server component of envibe. It gives AI coding assistants controlled access to your environment variables with 5 access levels:
| Level | AI Can See | AI Can Modify |
|---|---|---|
full | Actual value | Yes |
read-only | Actual value | No |
placeholder | <VAR_NAME> | No |
schema-only | Format only | No |
hidden | Nothing | No |
| Tool | Description |
|---|---|
env_list | List visible variables with access levels |
env_get | Get a variable's value (respects permissions) |
env_set | Set a variable (only full access) |
env_describe | Get detailed info including format and example |
env_check_required | Check which required variables are missing |
env_check_required to guide users through setupIf you need CLI commands like envibe setup -i (interactive mode), envibe view, or envibe generate, install the full package:
npm install -g envibe
MIT
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y envibe-mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-dominic-righthere-envibe": {
"command": "npx",
"args": [
"-y",
"envibe-mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referenceenvibe-mcpnpmio.github.dominic-righthere/envibe works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.