Immich Photo Manager MCP Server

If your Immich library has grown past what you can manage by hand, immich-photo-manager gives any AI assistant direct access to your instance — search, organize, deduplicate, and curate albums through natural. That is what the immich photo manager mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The tools it exposes

The server publishes 3 tools. What each one is for:

• Client — Status
• Document — Description
• Prerequisites — The Prerequisites tool exposed by this server

What it needs from you

Configuration is passed through the environment: IMMICH_BASE_URL, IMMICH_API_KEY. 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.

• A running Immich instance (self-hosted, v1.90+) - An Immich API key (how to create one) - Python 3.10+ with pip (download)

Getting it running

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

How it compares

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Immich Photo Manager's toolset — Client, Document, Prerequisites — is a fair guide to whether it matches your workflow. It is maintained by drolosoft; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Immich Photo Manager's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

• 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.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.