Move from .env files to Envlet

Sign in once

Install the CLI and sign in. It shows a URL and a code; approve in the browser and you are in.

npm install -g @envlet/cli
envlet login

Create the project and link the repo

In the dashboard, create a project with development, staging, and production environments. Then link the repository so every command in it knows which environment to use.

envlet init writes a small .envlet file at the repo root. It holds names, not values, so commit it.

envlet init

Import the values

Set each value once with envlet set, or import the whole file with the MCP server.

envlet set DATABASE_URL=postgres://...
envlet set STRIPE_KEY=sk_live_...

Run through Envlet

Put envlet run -- in front of the command you already use. Nothing else changes.

Then delete the .env files.

envlet run -- npm run dev

Or say the word

With the Envlet MCP server in Claude Code, Cursor, or Codex, this whole guide is one sentence: move us to Envlet. The agent does every step above, and no value ever enters the conversation.

claude mcp add --scope user envlet -- npx -y @envlet/cli mcp