Envault MCP Server

Secure secret management with a Human-In-The-Loop (HITL) interceptor for agent mutations. Exposed over MCP by the envault mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

Envault natively supports the Model Context Protocol (MCP), so AI coding assistants like Claude Desktop, Cursor, and RooCode/Cline can pull and push your secure environments effortlessly.

• Bank-Grade Security — AES-256-GCM encryption with master/data key hierarchy and automatic key rotation
• Project Workspaces — Organize secrets into distinct projects for better management
• Semantic Routing — Clean, GitHub-style URLs (/[username]/[project-slug]) for easy sharing and navigation
• Team Collaboration — Secure project sharing with strict Role-Based Access Control:
• Owner: Full administrative control (Rename, Delete, Manage Team)
• Editor: Active contributor (Read/Write secrets, request to Share)

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Its toolset

Everything the assistant can do here goes through one of these:

• Installation — Homebrew cask installs are deprecated. If you installed via cask, migrate with:
• Prerequisites — The Prerequisites tool exposed by this server

Configuration

You will need 8 environment variables: ENVAULT_CLI_URL, ENVAULT_BASE_URL, NEXT_PUBLIC_SUPABASE_URL, NEXT_PUBLIC_SUPABASE_ANON_KEY, ENCRYPTION_KEY, SUPABASE_SERVICE_ROLE_KEY, UPSTASH_REDIS_REST_URL, UPSTASH_REDIS_REST_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Node.js 18+ installed - A Supabase project set up

Caveats

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the envault mcp server does with a few real requests.

When to reach for it

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Envault's toolset — Installation, Prerequisites — is a fair guide to whether it matches your workflow. It is maintained by DinanathDash; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.