Move from .env files to Envlet

1. 01

   Sign in once

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

   Terminal

   npm install -g @envlet/cli
   envlet login

2. 02

   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.

   Terminal

   envlet init

3. 03

   Import the values

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

   Terminal

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

4. 04

   Run through Envlet

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

   Then delete the .env files.

   Terminal

   envlet run -- npm run dev

5. 05

   Or run the migrate prompt

   With the Envlet MCP server in Claude Code, Cursor, or Codex, the migrate prompt does every step above. Values never enter the conversation.

   Claude Code

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

Related

• Quickstart
• MCP server