
Enigmagent Mcp
Keeps your API keys out of LLM context by storing them in a local AES-256-GCM vault and resolving placeholders like {{OPENAI_KEY}} at the MCP boundary. Exposes two tools: enigmagent_resolve to decrypt secrets and enigmagent_list to show what's stored. Every secret is pinned to a domain, so the resolver only returns values when the origin matches. Works with Claude Desktop, Cursor, Continue.dev, Cline, and anything else that speaks MCP over stdio. Also runs in REST mode if you need it behind a proxy. Reach for this when you're building agents that call third-party APIs and you don't want tokens living in chat logs or conversation history.
- GitHub stars
- 2
- tools
- 2
- auth
- Secret needed
- transport
- STDIO
- env vars
- 2
- last updated
- Apr 25, 2026
Tools
2 toolsPublic tool metadata for what this MCP can expose to an agent.
enigmagent_listLists names, domains, and creation timestamps only.
Lists names, domains, and creation timestamps only.
No parameter schema in public metadata yet.
enigmagent_resolveReturns a value only when the requested origin matches the entry's domain binding.
Returns a value only when the requested origin matches the entry's domain binding.
No parameter schema in public metadata yet.
Sponsors
Configuration
VAULT_PASSWORDsecretMaster password used to decrypt the local EnigmAgent vault (AES-256-GCM + Argon2id).
VAULT_PATHPath to the vault.json file (default: ./vault.json).
Readme
enigmagent-mcp 2.0.0
enigmagent-mcp is a local encrypted vault server for MCP-capable clients. It
stores secret values with an Argon2id-derived AES-256-GCM key and keeps the
vault file encrypted at rest.
Version 2.0.0 makes the security boundary explicit:
- MCP starts in metadata-only mode. Raw secret resolution is disabled unless the
operator passes
--allow-raw-resolveor setsENIGMAGENT_ALLOW_RAW_RESOLVE=1. - REST binds to
127.0.0.1and requires a 32–256 character Bearer token. - REST requests have bounded headers, bodies, and timeouts; responses do not include arbitrary exception messages or permissive browser CORS.
- Vault writes use a temporary file, flush, replacement, and a recovery backup.
- Version 1 vaults remain readable. New vaults use format version 2 and the
versioned KDF context
enigma/v2.
Raw resolution is deliberately an opt-in escape hatch. A caller-declared origin is not proof of the network destination, and a trusted MCP client can still pass returned plaintext to its model. Do not enable raw resolution for an untrusted client or a shared process.
Details
- Repository
- github.com/agnuxo1/enigmagent-mcp
- Package
enigmagent-mcp- Transport
- STDIO
- Auth
- Required
- Registry
- MCP registry, active