Envibe
Let AI agents read or use environment variables only through an explicit permission layer instead of unfettered .env access.
Overview
Envibe is a MCP server for the Ship phase that provides a secure permission layer between AI agents and your .env files.
What is this MCP server?
- Permission layer between MCP-capable agents and local .env files
- npm package envibe-mcp (v0.2.7) with stdio MCP transport
- Reduces risk of agents dumping or leaking secrets during codegen and debugging
- GitHub-hosted envibe-mcp project for policy and updates
- Targets solo builders who already keep keys in .env during local ship prep
- Package version 0.2.7 on npm (identifier envibe-mcp)
- Transport: stdio
- Repository: github.com/dominic-righthere/envibe-mcp
What problem does it solve?
Agents with file access can accidentally read or echo .env secrets during innocent-looking coding requests.
Who is it for?
Solo builders using local .env files who still want agent help but need a deliberate gate before secrets leave disk.
Skip if: Teams with no .env workflow, fully centralized secret vaults only, or agents never granted environment-related tasks.
What do I get? / Deliverables
After registering envibe-mcp, environment values flow through MCP permissions so you can limit what the agent can see or use.
- Policy-controlled env access paths for agents via MCP
- Reduced blast radius when assistants work near credentials
Recommended MCP Servers
Journey fit
How it compares
Agent-focused .env permission MCP, not a cloud secret manager or static code scanner.
Common Questions / FAQ
Who is Envibe for?
Solo and indie developers who run AI coding agents against projects that store credentials in .env and want mediated access instead of open file reads.
When should I use Envibe?
Use it during ship and security hardening when you are wiring MCP tools and need to reduce accidental secret leakage from agent sessions.
How do I add Envibe to my agent?
Install the npm package envibe-mcp, add it as an stdio MCP server in Claude Code, Cursor, or your host’s config, then configure Envibe’s permission rules for which env keys agents may request.