Envibe MCP Server

Secure permission layer between AI agents and your .env files

Local serverstdio

What is the Envibe MCP server?

Secure permission layer between AI agents and your .env files. Exposed over MCP by the envibe mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

Add to claude_desktop_config.json: - macOS: ~/Library/Application Support/Claude/claude_desktop_config.json - Windows: %APPDATA%\Claude\claude_desktop_config.json

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

Its toolset

Everything the assistant can do here goes through one of these:

  • 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

Adding it to your client

Installation goes through your MCP client rather than a global install: point it at envibe-mcp on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Envibe's toolset — env_list, env_get, env_set and 2 more — is a fair guide to whether it matches your workflow. It is maintained by dominic-righthere; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Envibe's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the envibe mcp server does with a few real requests.

Available tools

ToolWhat it does
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

How to install the Envibe MCP server

{
  "mcpServers": {
    "envibe": {
      "command": "npx",
      "args": ["envibe-mcp"]
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Example prompts to try

  • Use Envibe to env list.
  • Use Envibe to env get.
  • Use Envibe to env set.

Frequently asked questions

It connects Envibe to MCP-compatible AI assistants such as Claude and Cursor, exposing 5 tools (env_list, env_get, env_set, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Envibe directly.