immich-mcp
Related Servers
Alternatives to immich-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables MCP clients to interact with a self-hosted comic/library server through its HTTP API, exposing libraries, series, books, collections, readlists, metadata, and administrative operations with read/write safety controls over stdio or Streamable HTTP.7MIT
- AlicenseCqualityCmaintenanceIt exposes the full official Immich API (276 tools across 41 groups) to MCP clients, letting them search and manage assets, albums, people, tags, memories, shared links, users, jobs and admin settings. It supports file uploads and downloads, stdio or streamable HTTP transports, and filtering/read-only safety modes.276MIT
- AlicenseBqualityBmaintenanceConnects MCP clients to a self-hosted Seafile server through the seahub HTTP API, exposing libraries, files, search, sharing, and optional admin operations over stdio or Streamable HTTP. It defaults to read-focused tools and gates writes behind confirmation, with token redaction and dry-run previews.4MIT
- AlicenseCqualityBmaintenanceEnables MCP clients to manage a media library, review duplicate-cleanup galleries, run workflows, and create generations through a local server authenticated with the user's account.66MIT
- AlicenseAqualityBmaintenanceConnects MCP clients to a self-hosted Syncthing instance's GUI REST API for reading configuration, folders, devices, and connections, plus gated write actions like adding or patching folders and devices, scanning, pausing, restarting, and shutting down. Supports stdio and localhost-only Streamable HTTP with API-key auth, dry-run write previews, redaction of secrets, caching, and rate limiting.5MIT
- AlicenseBqualityCmaintenanceEnables MCP clients to browse and manage a self-hosted photo gallery through its /api/v2 routes, with read-only defaults, configurable toolsets, caching, and confirmation-gated writes.7MIT
TDQS
Scored across 5 tools
The five tools are split along clear domain lines (albums, assets, people, search, server), so an agent can generally pick the right tool. However, boundaries blur at the edges: search_asset_statistics vs get_asset_statistics, get_map_markers vs get_album_map_markers, and search_person vs get_all_people create cross-tool overlap, and each tool multiplexes 13-43 actions behind one name, so action-level selection still requires careful reading.
Every tool uses the same immich_<domain> snake_case pattern, and the embedded action names inside each tool follow a consistent verb_noun convention (get_album_info, create_album, delete_album). No camelCase or mixed-verb anomalies anywhere in the surface.
Five tools is a reasonable, well-scoped count for an Immich API wrapper and keeps the top-level list small. The trade-off is that immich_assets alone bundles 43 operations, making individual tools quite heavy compared to the 3-15 tool ideal.
Core domains of the Immich API are covered end-to-end: albums, assets, people/faces, search/timeline, and server config/licensing. Entire areas such as tags, memories, shared links, activities, and user/admin management are absent, but these are secondary to the primary photo-library workflows.