MCP server for encrypted SQLite databases (SQLCipher 4) - Works with MoneyMoney, KeePass and more
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent β or use 1-click editor setup below.
π‘ Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
MCP server for encrypted SQLite databases
A Model Context Protocol (MCP) server for working with encrypted SQLite databases using SQLCipher. This server provides tools to read database structures, query tables, and perform CRUD operations on encrypted SQLite databases.
Compatible with all MCP clients (Cursor, Claude Desktop, and others).
Works with encrypted databases from: MoneyMoney, 1Password, Signal, WhatsApp, Firefox, Telegram, KeePass, and other applications using SQLCipher encryption.
MCP_DEBUG environment variableMany popular applications use encrypted SQLite databases (SQLCipher) to protect sensitive data. This MCP server is specifically designed to work with these encrypted databases.
If you need to access data from any of these applications or other SQLCipher-encrypted databases, this MCP server provides the tools you need. Note that you need the passphrase of the encrypted database.
sqlite-jdbc-3.50.1.0.jar from sqlite-jdbc-crypt)The easiest way to install this MCP server in Cursor is via the Cursor MCP Store:
This server works with any MCP-compatible client. See the Configuration section below for setup instructions.
Use the pre-built Docker image from GitHub Container Registry:
docker pull ghcr.io/rosch100/mcp-encrypted-sqlite:latest
Quick Start: See DOCKER_QUICKSTART.md for Docker Desktop setup.
Detailed Configuration: See DOCKER_CONFIGURATION.md for advanced options.
Clone the repository:
git clone https://github.com/rosch100/mcp-encrypted-sqlite.git
cd mcp-encrypted-sqlite
Build the project:
./gradlew build installDist
The build process will automatically download sqlite-jdbc-3.50.1.0.jar from sqlite-jdbc-crypt releases and place it in the libs/ directory.
The executable will be available at build/install/mcp-encrypted-sqlite/bin/mcp-encrypted-sqlite.
This MCP server works with any MCP-compatible client (Cursor, Claude Desktop, etc.). The configuration format follows the Model Context Protocol specification.
The server communicates via STDIO (standard input/output). Add the following configuration to your MCP client's configuration file:
Configuration file locations:
~/.cursor/mcp.json~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonOptional Parameters:
transport: Defaults to "stdio" (can be omitted)cwd: Not needed when using absolute paths (can be omitted)immutable: Optional boolean in the --args JSON. When true, opens the DB with SQLite URI file:β¦?immutable=1 (no file locks). Use for peeking at DBs locked exclusively by another app (e.g. MoneyMoney). All write tools/SQL are disabled in this mode (insert_or_update / delete_rows omitted; execute_sql accepts read-only statements only).env: Only needed if Java is not in your system PATH or for custom Java installation:When using encrypted passphrases, you must pass the encryption key as an environment variable:
Important Notes:
-e flag must come before the -v flagsecurity find-generic-password -s "mcp-encrypted-sqlite" -a "encryption-key" -w:ro) by default. Remove :ro if you need write accessSecurity Warning: Storing both the encryption key and encrypted passphrase as plain text in your configuration file is a security risk. See DOCKER_CONFIGURATION.md for secure alternatives.
Override the default SQLCipher 4 settings by including a cipherProfile in the configuration JSON:
Note: All fields in cipherProfile are optional - only specify the ones you want to override from the defaults. You can also specify cipherProfile in individual tool calls, but it's recommended to configure it once in the MCP server configuration for consistency.
For enhanced security, you can store passphrases in encrypted form. The server uses AES-256-GCM encryption, which provides authenticated encryption and is both secure and fast.
Generate and store key in Keychain:
Run: ./store-key-in-keychain.sh --generate
Encrypt your passphrase:
Run: ./encrypt-passphrase.sh "your-plain-passphrase"
The key is automatically loaded from the Keychain when no environment variable is set.
Benefits:
Generate an encryption key:
Run: java -cp build/libs/mcp-encrypted-sqlite-VERSION.jar com.example.mcp.sqlite.config.PassphraseEncryption
Set the encryption key:
Run: export MCP_SQLITE_ENCRYPTION_KEY="<your-generated-key>"
Encrypt your passphrase:
Run: java -cp build/libs/mcp-encrypted-sqlite-VERSION.jar com.example.mcp.sqlite.util.EncryptPassphrase "your-plain-passphrase"
Use the encrypted passphrase (with encrypted: prefix) in your configuration:
No reviews yet β be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/mcp-encrypted-sqlite)<a href="https://allmcps.com/mcp/mcp-encrypted-sqlite"><img src="https://allmcps.com/api/badge/mcp-encrypted-sqlite?style=directory" alt="MCP Encrypted Sqlite on AllMCPs" /></a>