Veracrypt MCP Server

MCP server to mount and unmount VeraCrypt containers with secure stdin password handling.

Local serverstdioPython

What is the Veracrypt MCP server?

If you already use Veracrypt, the veracrypt mcp server is the piece that lets your assistant work with it directly. MCP server to mount and unmount VeraCrypt containers with secure stdin password handling.

What the server does

MCP (Model Context Protocol) server for mounting and unmounting VeraCrypt containers, with a security-first approach to password handling.

  • mount_container — mount a VeraCrypt container (optional mount point, PIM, read-only)
  • unmount_container — dismount by container path or mount point
  • list_mounted_containers — show all mounted VeraCrypt volumes
  • Default vault — configure your container once via environment variables; "mount my vault" then works without any arguments

Installation

git on PyPI is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Credentials and setup notes

Configuration is passed through the environment: VERACRYPT_MCP_CONTAINER, VERACRYPT_MCP_KEYCHAIN_ACCOUNT, VERACRYPT_PATH. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

  • Python >= 3.10 - VeraCrypt with the command line binary available (veracrypt on PATH, the macOS app bundle, or set VERACRYPT_PATH) - macOS: macFUSE (required by VeraCrypt for mounting) - Linux keyring source: libsecret-tools (secret-tool)

Worth knowing first

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. It is maintained by bitterdev; 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.

How to install the Veracrypt MCP server

{
  "mcpServers": {
    "veracrypt": {
      "command": "veracrypt-mcp",
      "env": {
        "VERACRYPT_MCP_CONTAINER": "/path/to/vault.hc",
        "VERACRYPT_MCP_KEYCHAIN_ACCOUNT": "my-vault"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

  • Python >= 3.10 - VeraCrypt with the command line binary available (veracrypt on PATH, the macOS app bundle, or set VERACRYPT_PATH) - macOS: macFUSE (required by VeraCrypt for mounting) - Linux keyring source: libsecret-tools (secret-tool)
VariableDescriptionRequired
VERACRYPT_MCP_CONTAINERConfiguration value read at startup.Optional
VERACRYPT_MCP_KEYCHAIN_ACCOUNTCredential the server authenticates with.Yes
VERACRYPT_PATHFilesystem location the server is allowed to use.Optional

Frequently asked questions

It connects Veracrypt to MCP-compatible AI assistants such as Claude and Cursor. Instead of copying data back and forth by hand, the assistant works with Veracrypt directly.