MCP server for an Immich photo library: CLIP smart + metadata search, people, albums, places, viewable images, gallery exports, library analysis and optional curation
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"immich-library-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# immich-library-mcp [MCP](https://modelcontextprotocol.io) server for an [Immich](https://immich.app) photo library (built against Immich v3.3.3). It lets an agent search the library by content (CLIP smart search) or by metadata, read EXIF/people/album/tag detail, count and map the library, **look at the photos themselves** (preview/thumbnail images and numbered contact sheets returned as MCP image content), analyse it (duplicates, largest files, stacks, activity, processing queues), **export browser-ready files plus a metadata manifest**, stage originals on a shared mount for other MCP servers and, with a second key, **organise** it (favourites, ratings, descriptions, dates, locations, tags, albums, people, uploads, reprocessing). Two keys, two trust levels: - **`IMMICH_API_KEY` (always): read-only.** Scope it to read permissions only, so Immich itself refuses writes (the integration suite asserts a `403` on album create). With only this key the server is read-only: the curation tools are not registered at all, and the only writes are local files (the shared mount and the export folder). - **`IMMICH_WRITE_API_KEY` (optional): curation.** Scoped to exactly the 13 write permissions the curation tools use and **no read permissions**, so every lookup still goes through the read key. It cannot delete or trash photos, share anything, or touch admin settings (the integration suite asserts `403`s on `/server/about`, `DELETE /assets` and `POST /shared-links`). Give it only to clients that should organise the library; a shared HTTP deployment (chat front ends, automation) can run without it. ## Install ```bash uvx immich-library-mcp --stdio # or: pip install immich-library-mcp ``` The distribution is `immich-library-mcp` (the name `immich-mcp` on PyPI belongs to another project); the import package is `immich_mcp`, and both `immich-library-mcp` and `immich-mcp` commands are installed. Claude Desktop / Claude Code (stdio): ```json {"mcpServ…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.