Env Var Locker
Env-Var-Locker is an MCP server that manages encrypted environment variables for agents with zero-leak-oriented access.
About
Env-Var-Locker is an MCP server for encrypted environment variable management aimed at developers who paste secrets into.env files and worry every time an AI agent reads project context. Registering the remote endpoint lets compatible agents interact with stored variables through a locker designed around zero-leak behavior rather than ad hoc copy-paste from password managers. For a founder, that reduces the chance of accidental exposure in commits, screen shares, or long chat threads during Ship and early Operate. The integration is task-specific: it does not replace a full secrets manager for large teams but gives agent workflows a controlled channel for env access. Documentation in the manifest is minimal; treat capabilities as described—encryption and leak prevention—until you validate against your threat model. Use alongside git-secrets scanning and never substitute human review for production key rotation.
- Encrypted environment variable manager advertised with zero-leak capabilities
- Remote MCP SSE at env-locker-mcp.vercel.app (v1.0.0)
- Premium settlement via optional EIP-3009 payment-signature header
- Keeps API keys and tokens out of plaintext prompts when agents need config
Env Var Locker by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
claude mcp add --transport sse env-locker https://env-locker-mcp.vercel.app/api/mcp --header "payment-signature: YOUR_PAYMENT_SIGNATURE"Add your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| Transport | SSE |
|---|---|
| Auth | Required |
What it does
Let your agent manage and retrieve encrypted environment variables without leaking secrets into chat logs or repos.
Who is it for?
Best when you're shipping SaaS or APIs and want MCP-driven env access without dumping keys into every agent turn.
Skip if: Organizations already standardized on Vault or cloud secret managers with strict IAM and audit you will not duplicate via MCP.
What you get
Agents can work with encrypted env storage so fewer secrets sit in plaintext files and chat history.
- Agent-mediated access to encrypted env variables
- Reduced reliance on plaintext .env in agent sessions
- Configured remote Env-Var-Locker MCP endpoint
By the numbers
- Server version 1.0.0 in published MCP manifest
- 1 SSE remote URL on Vercel
- 1 secret header slot: payment-signature (EIP-3009)
Recommended MCP Servers
1Claw VaultHSM-backed vault secrets for AI agents (JIT fetch) plus prompt-injection and threat scanning.2
1passwordMCP server for 1Password service accounts — tools and resources for vaults and credentials18
402sentinel McpAssess an x402 counterparty's risk BEFORE paying: allow/review/block, scored on-chain (Base).1
A2adependencyinspector McpRemote MCP for A2A dependency inspector MCP, structured receipts, audit logs, and reviewer-ready eviA2a Governance Bridge McpA2A Governance Bridge MCP server.A2aidentitytoll McpRemote MCP for A2A caller identity, scope policy, verdict receipts, and audit history.How it compares
MCP secrets locker integration, not a local .env generator skill or broad compliance audit suite.
FAQ
Who is Env Var Locker for?
Developers and small teams using Claude Code or Cursor who need encrypted env vars reachable by MCP without exposing secrets in prompts.
When should I use Env Var Locker?
Use it during Ship and early Operate when you configure staging and production secrets and want agents to reference env values through an encrypted locker.
How do I add Env Var Locker to my agent?
Add https://env-locker-mcp.vercel.app/api/mcp as an SSE MCP server in your agent settings; supply payment-signature only if your plan requires EIP-3009 premium settlement.