Back to Directory/Developer Tools

io.github.dominic-righthere/envibe

Secure permission layer between AI agents and your .env files

Developer ToolsTypeScriptv0.2.7

envibe-mcp

npm version License: MIT

MCP server for envibe - the missing permission layer between AI agents and your .env.

Install

Add to your AI tool's MCP config:

{
  "mcpServers": {
    "envibe": {
      "command": "npx",
      "args": ["envibe-mcp"]
    }
  }
}
Claude Code
claude mcp add envibe npx envibe-mcp
Claude Desktop

Add to claude_desktop_config.json:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json
VS Code / Cursor / Windsurf

Add to your editor's MCP settings (see main envibe docs for details).

On first run, envibe automatically:

  1. Creates .env.manifest.yaml from your .env.example
  2. Generates .env.ai (filtered view for AI)
  3. Blocks direct .env file access

What is this?

This is the MCP server component of envibe. It gives AI coding assistants controlled access to your environment variables with 5 access levels:

LevelAI Can SeeAI Can Modify
fullActual valueYes
read-onlyActual valueNo
placeholder<VAR_NAME>No
schema-onlyFormat onlyNo
hiddenNothingNo

MCP Tools

ToolDescription
env_listList visible variables with access levels
env_getGet a variable's value (respects permissions)
env_setSet a variable (only full access)
env_describeGet detailed info including format and example
env_check_requiredCheck which required variables are missing

v0.2.0 Features

  • Better error messages - When access is denied, get helpful guidance
  • Format hints - Know what format a variable should be (url, key, number, etc.)
  • Required var checking - Use env_check_required to guide users through setup

For CLI tools

If you need CLI commands like envibe setup -i (interactive mode), envibe view, or envibe generate, install the full package:

npm install -g envibe

License

MIT

Installation

Source-derived launch command. Check the maintainer’s required arguments and credentials before running:

bash
npx -y envibe-mcp

Set up in your AI client

Merge 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.

json
{
  "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 reference

Package

envibe-mcpnpm

Compatible MCP Clients

io.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.

  • Claude Desktop~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.
  • Cursor~/.cursor/mcp.jsonRestart Cursor for changes to take effect.
  • VS Code.vscode/mcp.jsonReload VS Code window for changes to take effect.
  • Windsurf~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect.
  • Claude Code.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.

Learn More