Immich Photo Manager

Immich Photo Manager runs locally from a Python package published to PyPI: immich-photo-manager version 2.0.11. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install — the usual command is uvx immich-photo-manager. It reads these environment variables: IMMICH_BASE_URL (required) and IMMICH_API_KEY (required, secret); set them in the client's configuration for this server.

Immich Photo Manager runs locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: ghcr.io/drolosoft/immich-photo-manager:2.0.11. The package starts a local server that speaks MCP over Streamable HTTP; the client then connects to it by URL (the entry names docker as the runtime). It reads these environment variables: IMMICH_BASE_URL, IMMICH_API_KEY (secret) and MCP_ALLOWED_HOSTS; set them in the client's configuration for this server. Required arguments: -p.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "immich-photo-manager": {
      "command": "uvx",
      "args": [
        "immich-photo-manager"
      ],
      "env": {
        "IMMICH_BASE_URL": "<value>",
        "IMMICH_API_KEY": "<secret>"
      }
    }
  }
}

Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect