Agents

Envlet for Cursor

Cursor 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.

Install
{
  "mcpServers": {
    "envlet": {
      "command": "npx",
      "args": ["-y", "@envlet/cli", "mcp"]
    }
  }
}
Run with its own identity
envlet run -- cursor .
Say the word
Move us to Envlet.

Set up

  1. 01

    Add the MCP server

    Add the entry to your Cursor MCP settings, then reload the window.

  2. 02

    Give it an identity

    Create an agent identity for Cursor in the dashboard or let the migrate prompt do it. Its token opens one environment, and production starts fully withheld.

  3. 03

    Run it through Envlet

    Start Cursor with envlet run. It sees the values for its identity and nothing else, and every read shows up under its name.

Questions

Can Cursor read production secrets?
Not by default. A new agent grant withholds every current and future production variable. You allow specific names when you decide to.
Do agent identities count toward my plan?
No. Agents and CI identities are unlimited on every plan. Only humans are members.

Stop pasting .env files.

One command. The right values for whoever runs it.