Envibe

Name: Envibe
Author: dominic-righthere

@dominic-righthereMCP server · External

Secure permission layer between AI agents and your .env files

AI agent governancev0.2.7TypeScript

Freeno charge per call

How to install

Runs on your machine from its package; the steps are below.

What it does

Reads
Writes
High impact

At most: creates or changes data: records, files, settings.

What it costs

Free

Odel charges nothing per call. The publisher may charge for its own service.

Runs locally over stdio

This server isn't hosted — your MCP client launches it from a package registry. Use one of the commands below, or drop the config into your client (e.g. Claude Desktop).

npmenvibe-mcpv0.2.7

Run

npx -y envibe-mcp

MCP client config

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

README1 min readView on GitHub

envibe-mcp

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

Install

Add to your AI tool's MCP config:

json

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

Claude Code

bash

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:

Creates .env.manifest.yaml from your .env.example
Generates .env.ai (filtered view for AI)
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:

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

MCP Tools

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

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