English Français العربية

io.github.Agnuxo1/enigmagent-mcp

Official registry Security

Local AES-256-GCM vault for AI agents. Secrets stay local, LLMs never see real API keys.

Source code Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

NPM package enigmagent-mcp
Claude Code 
claude mcp add enigmagent-mcp -e 'VAULT_PASSWORD=<your vault_password>' -e 'VAULT_PATH=<VAULT_PATH>' -- npx -y enigmagent-mcp@1.0.2
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "enigmagent-mcp": {
            "command": "npx",
            "args": [
                "-y",
                "enigmagent-mcp@1.0.2"
            ],
            "env": {
                "VAULT_PASSWORD": "<your vault_password>",
                "VAULT_PATH": "<VAULT_PATH>"
            }
        }
    }
}

Environment variables

  • VAULT_PASSWORD secret Master password used to decrypt the local EnigmAgent vault (AES-256-GCM + Argon2id).
  • VAULT_PATH Path to the vault.json file (default: ./vault.json).

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. enigmagent-mcp 2.0.0
  2. Install and run
  3. MCP modes
  4. Authenticated REST
  5. Client configuration adapters
  6. Development and verification
  7. Release contents
  8. Scope and threat model

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-resolve or sets ENIGMAGENT_ALLOW_RAW_RESOLVE=1.
  • REST binds to 127.0.0.1 and 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.

Install and run

npx enigmagent-mcp@2.0.0 --vault ./my.vault.json

The first run prompts for the existing vault credentials when attached to a terminal. For a trusted headless process, set ENIGMAGENT_USER and ENIGMAGENT_PASS in its private environment. The server does not print either value.

MCP modes

The stdio transport implements bounded JSON-RPC MCP initialization, ping, tools/list, and tools/call. The default tool is:

  • enigmagent_list: names, domains, and creation timestamps only.

With explicit raw-resolution opt-in, it additionally exposes:

  • enigmagent_resolve: returns a value only when the requested origin matches the entry's domain binding.

The origin is normalized and limited to HTTP(S) URLs without embedded user credentials. Notifications, malformed JSON, oversized frames, invalid tool arguments, and calls before initialization are handled without terminating the process.

Authenticated REST

set ENIGMAGENT_API_TOKEN=use-a-random-32-character-token-or-longer
npx enigmagent-mcp@2.0.0 --mode rest --port 3737 --vault ./my.vault.json

GET /health is a minimal unauthenticated liveness check. GET /status and GET /list require Authorization: Bearer <token>. POST /resolve also requires the token, JSON content type, and the explicit raw-resolution flag. The service rejects browser-origin requests and binds only to loopback.

Client configuration adapters

integrations.js provides tested configuration builders for Claude Desktop, Cursor, Continue, Cline, Open WebUI, AnythingLLM, LM Studio, Zed, Goose, and Windsurf. They are maintained configuration examples using the standard MCP stdio command; they are not upstream plugins, endorsements, or claims of adoption by those projects.

Development and verification

npm ci
npm test
npm run check
npm run benchmark
npm pack --dry-run

The tests cover encrypted-at-rest behavior, domain matching, wrong credentials, version-1 migration reads, backup recovery, bounded MCP framing and session ordering, authenticated REST, and all ten configuration adapters. The benchmark uses synthetic data and reports create/add/resolve latency without printing a secret.

Release contents

The historical 1.0.5 tree is preserved in versions/1.0.5/ with its source archive and SHA-256 manifest. The 2.0.0 release is represented consistently in package.json, server.json, and manifest.json; publication remains subject to the repository's CI and release checks.

Scope and threat model

This project protects vault contents from ordinary plaintext-at-rest exposure and from accidental return by the metadata listing tool. It does not protect against a compromised operating system, a process with access to the unlocked memory, malicious client code, side channels, swap/core dumps, or an operator who explicitly enables raw resolution for an untrusted model. Review SECURITY.md in the main EnigmAgent project for broader ecosystem guidance.

MIT licensed. See LICENSE.

Frequently asked questions

What is io.github.Agnuxo1/enigmagent-mcp?

Local AES-256-GCM vault for AI agents. Secrets stay local, LLMs never see real API keys.

How do I install io.github.Agnuxo1/enigmagent-mcp?

It runs on your machine. In Claude Code: claude mcp add enigmagent-mcp -e 'VAULT_PASSWORD=<your vault_password>' -e 'VAULT_PATH=<VAULT_PATH>' -- npx -y enigmagent-mcp@1.0.2. For other clients, paste the JSON configuration from this page into their MCP settings.

Does io.github.Agnuxo1/enigmagent-mcp need an API key?

Yes. It expects VAULT_PASSWORD, which you set in its configuration.

Is io.github.Agnuxo1/enigmagent-mcp open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains io.github.Agnuxo1/enigmagent-mcp?

It is published by Agnuxo1. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.