Skip to main content
Glama
Sign In
immich-mcp

immich-mcp

by si-essence
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

immich_server

DestructiveIdempotent

Retrieves Immich server information, configuration, features, statistics, storage, media types, version, and license status; can set or delete the product key with confirm-gated writes.

Instructions

immich_server covers the server toolset (16 operations). Auth header x-api-key. Writes need confirm:true and IMMICH_ALLOW_WRITES=true. Omit confirm for a dry-run preview. Actions: delete_server_license: DELETE /server/license. Delete server product key get_about_info: GET /server/about. Get server information get_apk_links: GET /server/apk-links. Get APK links get_public_config: GET /public/config. Get the public configuration get_public_config_defaults: GET /public/config/defaults. Get the public configuration defaults get_server_config: GET /server/config. Get config get_server_features: GET /server/features. Get features get_server_license: GET /server/license. Get product key get_server_statistics: GET /server/statistics. Get statistics get_server_version: GET /server/version. Get server version get_storage: GET /server/storage. Get storage get_supported_media_types: GET /server/media-types. Get supported media types get_version_check: GET /server/version-check. Get version check status get_version_history: GET /server/version-history. Get version history ping_server: GET /server/ping. Ping set_server_license: PUT /server/license. Set server product key

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "immich_server"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoJSON body for the Immich operation. Secrets are redacted in output.
queryNoOpenAPI query parameters.
actionYesImmich operation to call.
paramsNoOpenAPI path parameters, such as id.
confirmNoSet to the boolean true to execute the write. Omit this field for a dry-run preview. false and the string true are rejected.
checksumNoOptional x-immich-checksum header for asset upload.
file_pathNoLocal file to upload as multipart assetData. Confirm-gated. The path is omitted from output.
save_pathNoLocal path to save a binary download. If omitted, only metadata is returned. The path is omitted from output.
sidecar_pathNoOptional local XMP sidecar for asset upload. The path is omitted from output.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the destructive and open-world annotations, the description adds the auth requirement (x-api-key), the write confirmation and environment-variable gate, the dry-run behavior, and that secrets and file paths are redacted in output. These are meaningful behavioral details not present in the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description front-loads the critical auth and write-gating rules, but the action list is a dense run-on with inconsistent punctuation that can be hard to parse. The content is necessary for a 16-operation dispatcher, but better formatting would improve usability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 16-operation server tool with no output schema, the description covers the action set, authentication, write confirmation, dry-run behavior, and output redaction. It does not enumerate per-action body schemas, but that is reasonably delegated to the generic body/query parameters in the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds value by mapping each action enum value to a human-readable operation and HTTP endpoint, which helps the agent choose the right action. It also reinforces confirm behavior and mentions the API-key header, though most individual parameter semantics still rely on the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states that this tool covers the server toolset with 16 operations, and it lists each action mapped to its HTTP method and endpoint. This makes the resource scope clear, though it does not explicitly distinguish the tool from its siblings beyond the word 'server'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives operational guidance for writes: confirm:true plus IMMICH_ALLOW_WRITES=true, and omitting confirm gives a dry-run preview. However, it never says when to choose this tool over immich_albums, immich_assets, immich_people, or immich_search; the server-only scope is implied by the name and action list.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools