❯envpilot
featurespricing❯docsblogchangelogwishlistfaq
sign-inget-started
// documentation
Start Here
  • Quickstart
  • Core concepts
  • Architecture: the machine surfaces
Platform
  • Data model
  • Variables
  • Secret files
  • Shared Accounts
  • Secret Sharing Links
  • Diagrams in documentation
  • Sharing documentation
  • Roles & permissions
  • Requests & approvals
  • Protected environments
  • Rotation & expiry
  • Security
Plans & Limits
  • Plans & Limits
  • Rate limits
CLI
  • CLI overview
  • Authentication & accounts
  • Linking projects
  • Pull & push
  • Running commands with secrets
  • Single secrets
  • Requests
  • Secret files
  • Command reference
  • CLI in CI & troubleshooting
VS Code
  • VS Code overview
  • Linking & sync
  • Protection
  • Editor features
  • Commands
  • Settings
  • Troubleshooting
JetBrains
  • JetBrains overview
  • Linking & sync
  • Protection
  • Troubleshooting
GitHub Action
  • GitHub Action overview
  • Inputs & outputs
  • Secret files in CI
  • Recipes
  • Action security
Docker
  • Docker overview
  • Build time
  • Runtime
  • Docker Compose
  • Docker reference
API Reference
  • API overview
  • API Quickstart
  • Authentication
  • Errors
  • Organization
  • Projects
  • Variables
  • Shared accounts
  • Secret files
MCP Server
  • MCP overview
  • MCP setup
  • Connecting a client
  • Tools
  • Agent requests
  • API keys (legacy)
Web Dashboard
  • Dashboard overview
  • Working in a project
  • Organization administration
Integrations
  • Slack & Discord Notifications
Guides
  • How to Share Environment Variables Securely
  • Next.js Environment Variables Best Practices
  • Android keystore in CI
  • Giving an agent secrets safely

// resources

  • github
  • npm
  • vs code marketplace
  • jetbrains marketplace
Start HerePlatformPlans & LimitsCLIVS CodeJetBrainsGitHub ActionDockerAPI ReferenceMCP ServerWeb DashboardIntegrationsGuides
❯envpilot

Encrypted environment variables for teams that live in the terminal. No .env files, no secrets in Slack.

$npm install -g @envpilot/cli

// product

  • Features
  • Pricing
  • Changelog
  • Wishlist

// resources

  • Getting Started
  • CLI Reference
  • VS Code Extension
  • Security

// compare

  • vs Doppler
  • vs Infisical
  • vs .env files

// support

  • FAQ
  • Support
  • Contact
  • Docs
  • Status

// legal

  • Privacy Policy
  • Terms of Service

© 2026 Envpilot · Built at Syntax Lab Technology · Abdul Rafay

ENVPILOT

❯envpilot
featurespricing❯docsblogchangelogwishlistfaq
sign-inget-started
// documentation
Start Here
  • Quickstart
  • Core concepts
  • Architecture: the machine surfaces
Platform
  • Data model
  • Variables
  • Secret files
  • Shared Accounts
  • Secret Sharing Links
  • Diagrams in documentation
  • Sharing documentation
  • Roles & permissions
  • Requests & approvals
  • Protected environments
  • Rotation & expiry
  • Security
Plans & Limits
  • Plans & Limits
  • Rate limits
CLI
  • CLI overview
  • Authentication & accounts
  • Linking projects
  • Pull & push
  • Running commands with secrets
  • Single secrets
  • Requests
  • Secret files
  • Command reference
  • CLI in CI & troubleshooting
VS Code
  • VS Code overview
  • Linking & sync
  • Protection
  • Editor features
  • Commands
  • Settings
  • Troubleshooting
JetBrains
  • JetBrains overview
  • Linking & sync
  • Protection
  • Troubleshooting
GitHub Action
  • GitHub Action overview
  • Inputs & outputs
  • Secret files in CI
  • Recipes
  • Action security
Docker
  • Docker overview
  • Build time
  • Runtime
  • Docker Compose
  • Docker reference
API Reference
  • API overview
  • API Quickstart
  • Authentication
  • Errors
  • Organization
  • Projects
  • Variables
  • Shared accounts
  • Secret files
MCP Server
  • MCP overview
  • MCP setup
  • Connecting a client
  • Tools
  • Agent requests
  • API keys (legacy)
Web Dashboard
  • Dashboard overview
  • Working in a project
  • Organization administration
Integrations
  • Slack & Discord Notifications
Guides
  • How to Share Environment Variables Securely
  • Next.js Environment Variables Best Practices
  • Android keystore in CI
  • Giving an agent secrets safely

// resources

  • github
  • npm
  • vs code marketplace
  • jetbrains marketplace
Start HerePlatformPlans & LimitsCLIVS CodeJetBrainsGitHub ActionDockerAPI ReferenceMCP ServerWeb DashboardIntegrationsGuides
❯envpilot

Encrypted environment variables for teams that live in the terminal. No .env files, no secrets in Slack.

$npm install -g @envpilot/cli

// product

  • Features
  • Pricing
  • Changelog
  • Wishlist

// resources

  • Getting Started
  • CLI Reference
  • VS Code Extension
  • Security

// compare

  • vs Doppler
  • vs Infisical
  • vs .env files

// support

  • FAQ
  • Support
  • Contact
  • Docs
  • Status

// legal

  • Privacy Policy
  • Terms of Service

© 2026 Envpilot · Built at Syntax Lab Technology · Abdul Rafay

ENVPILOT

// documentation
Start Here
  • Quickstart
  • Core concepts
  • Architecture: the machine surfaces
Platform
  • Data model
  • Variables
  • Secret files
  • Shared Accounts
  • Secret Sharing Links
  • Diagrams in documentation
  • Sharing documentation
  • Roles & permissions
  • Requests & approvals
  • Protected environments
  • Rotation & expiry
  • Security
Plans & Limits
  • Plans & Limits
  • Rate limits
CLI
  • CLI overview
  • Authentication & accounts
  • Linking projects
  • Pull & push
  • Running commands with secrets
  • Single secrets
  • Requests
  • Secret files
  • Command reference
  • CLI in CI & troubleshooting
VS Code
  • VS Code overview
  • Linking & sync
  • Protection
  • Editor features
  • Commands
  • Settings
  • Troubleshooting
JetBrains
  • JetBrains overview
  • Linking & sync
  • Protection
  • Troubleshooting
GitHub Action
  • GitHub Action overview
  • Inputs & outputs
  • Secret files in CI
  • Recipes
  • Action security
Docker
  • Docker overview
  • Build time
  • Runtime
  • Docker Compose
  • Docker reference
API Reference
  • API overview
  • API Quickstart
  • Authentication
  • Errors
  • Organization
  • Projects
  • Variables
  • Shared accounts
  • Secret files
MCP Server
  • MCP overview
  • MCP setup
  • Connecting a client
  • Tools
  • Agent requests
  • API keys (legacy)
Web Dashboard
  • Dashboard overview
  • Working in a project
  • Organization administration
Integrations
  • Slack & Discord Notifications
Guides
  • How to Share Environment Variables Securely
  • Next.js Environment Variables Best Practices
  • Android keystore in CI
  • Giving an agent secrets safely

// resources

  • github
  • npm
  • vs code marketplace
  • jetbrains marketplace
Start HerePlatformPlans & LimitsCLIVS CodeJetBrainsGitHub ActionDockerAPI ReferenceMCP ServerWeb DashboardIntegrationsGuides
MCP overviewMCP setupConnecting a clientToolsAgent requestsAPI keys (legacy)
docs/MCP Server

Connecting a client

Claude, Claude Code, Codex, Cursor and VS Code, connected with your Envpilot login.

open in claudeopen in chatgptopen in cursor

Connecting a client

Every client uses the same URL, https://www.envpilot.dev/api/mcp, and no Authorization header. The client finds the sign-in on its own and opens your browser. For what happens next, see MCP setup.

Using an API key today? Follow Moving from an API key first.

Claude (web, Desktop, mobile, Cowork)#

  1. Open Customize → Connectors and choose Add custom connector. On Team and Enterprise plans an Owner adds it under Organization settings → Connectors.
  2. Enter https://www.envpilot.dev/api/mcp as the server URL. Leave the OAuth client fields empty.
  3. Select Connect and sign in to Envpilot in the window that opens.

Do not paste an Envpilot API key into an OAuth Client Secret field. That field authenticates an OAuth client during a token exchange; it never becomes the Authorization header on MCP requests.

Claude Code#

❯terminal
claude mcp add --transport http --scope user \
  envpilot https://www.envpilot.dev/api/mcp

Run /mcp in a session, choose envpilot, then Authenticate. A browser window opens for the Envpilot sign-in.

Choose the configuration scope deliberately:

  • --scope local (the default) keeps the server private to you in the current project.
  • --scope project writes .mcp.json for the team. It holds only the URL, so it is safe to commit; each person signs in for themselves.
  • --scope user makes it available to you across projects.

claude mcp list only confirms the server is saved. /mcp shows whether it is signed in and its tools loaded. claude mcp add does not overwrite an existing entry, so remove a key-based envpilot entry first with claude mcp remove envpilot.

Codex CLI, desktop, and IDE extension#

❯terminal
codex mcp add envpilot --url https://www.envpilot.dev/api/mcp
codex mcp login envpilot

Or add it to ~/.codex/config.toml and run codex mcp login envpilot:

❯toml
[mcp_servers.envpilot]
url = "https://www.envpilot.dev/api/mcp"

Leave out bearer_token_env_var; that is the old key setup. If your Codex version has no codex mcp login, update Codex. Run /mcp to confirm the Envpilot tools are present.

Cursor#

Add the server to ~/.cursor/mcp.json, or .cursor/mcp.json for a project:

❯json
{
  "mcpServers": {
    "envpilot": {
      "url": "https://www.envpilot.dev/api/mcp"
    }
  }
}

Open Cursor's MCP settings. The server shows that it needs a login; select it and sign in.

VS Code#

Add the server to .vscode/mcp.json in a workspace, or to your user MCP configuration:

❯json
{
  "servers": {
    "envpilot": {
      "type": "http",
      "url": "https://www.envpilot.dev/api/mcp"
    }
  }
}

Start the server from the MCP view and follow the sign-in prompt.

Other clients#

Any client that supports MCP authorization works: give it the URL and no header. It discovers the sign-in from the server's 401 response. A client that only supports static headers cannot connect; use the REST API or envpilot run for those jobs.

More than one organization#

If your account belongs to several organizations, pass organization (the organization's slug) to the project tools; envpilot_get_doc and envpilot_update_doc_draft take a doc id instead. The error message lists the slugs you can use.

Troubleshooting#

See MCP setup → Troubleshooting.

← mcp serverMCP setup
mcp server →Tools

// on this page

  • Claude (web, Desktop, mobile, Cowork)
  • Claude Code
  • Codex CLI, desktop, and IDE extension
  • Cursor
  • VS Code
  • Other clients
  • More than one organization
  • Troubleshooting