Envlet
LanguagesAgentsPlatformsGuidesDocsPricing
Start freeLog in
Start free

For every agent

Every coding agent gets its own identity, its own token, and its own line in the audit log. Production starts withheld.

  • Claude CodeAdd one MCP server and say move us to Envlet. Claude Code signs you in, creates the project, imports your .env files, and gives itself an identity with production withheld.Set up
  • CursorCursor gets the Envlet tools through one MCP entry and its own identity through one token, so it never sees a production value it was not given.Set up
  • CodexCodex reads its MCP servers from config.toml. One block adds Envlet, one token gives it an identity.Set up
  • WindsurfWindsurf's Cascade agent takes MCP servers from one JSON config. Give it Envlet, then run it with its own identity.Set up
  • GitHub CopilotCopilot agent mode in VS Code reads MCP servers from .vscode/mcp.json. Commit that file and every teammate's Copilot gets the same tools.Set up
  • Gemini CLIGemini CLI reads MCP servers from its settings file. One entry adds Envlet, one token gives it an identity.Set up
  • ZedZed's agent panel takes context servers from settings.json. Give it Envlet and run Zed with an identity of its own.Set up
  • ReplitReplit Agent runs in the cloud, so it gets Envlet through one secret rather than a local MCP server: an agent identity token in Replit Secrets.Set up

Stop pasting .env files.

One command. The right values for whoever runs it.

Start free
ENVLET
Envlet

Your project's env vars in one place, for everyone and everything that runs your code.

Product

  • Features
  • Languages
  • Agents
  • Platforms
  • Pricing

Learn

  • Guides
  • Compare
  • FAQ
  • Docs

Company

  • About
  • Changelog
  • Status
  • Contact

Trust

  • Security
  • Terms
  • Privacy
  • DPA
  • Subprocessors

Developers

  • GitHub
  • npm

© 2026 Envlet. All rights reserved.