ente-mcp: A CLI and MCP Server for Ente Photos, Auth, and Locker (Without Touching E2EE Keys)
Nov 17, 2026Giving an AI agent access to an end-to-end encrypted service usually goes wrong in one of two ways: either you hand your encryption keys to a third-party wrapper, or the tool dumps TOTP secrets straight into the model's context window.
ente-mcp is an unofficial CLI (ente-agent) and stdio MCP server (ente-mcp) for Ente Photos, Auth, and Locker—built around a strict rule: never reimplement Ente cryptography.
How it stays safe around E2EE
- Photos uploads via watch folders: Instead of trying to encrypt and upload blobs itself,
ente_queuedrops files (hardlink with copy fallback) into Ente Desktop's configured watch folders so the official desktop app encrypts and syncs them viadeduceEvents. - Official CLI for exports and Auth: Exports and Auth decryption shell out to the official
enteCLI.ente_auth_decryptwrites decrypted exports to disk rather than printing TOTP secrets to stdout, andente-agent exportcoordinates with desktop uploaders via astate/export-activelock so exports and watch-folder uploads never collide. - Plaintext-only Museum server ops: Tools like
ente_account,ente_sessions,ente_collections,ente_trash,ente_unshare, andente_public_linktalk toapi.ente.com(or a self-hosted endpoint) using only plaintext server state—tokens are redacted, album/file names remain encrypted, destructive trash operations requireconfirm=True, and anything requiring E2EE keys stays in the official apps.
Works as a CLI or MCP server
Install from GitHub (pip install git+https://github.com/aminamos/ente-mcp.git) or run with uv, then use ente-agent from the terminal or wire ente-mcp into any stdio MCP client.
Check out the repo at github.com/aminamos/ente-mcp.