local-image-convert-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOCAL_IMAGE_CONVERT_ROOT | Yes | The only directory the server may read from and write to. Required. Must be an absolute path. Refuses filesystem root, home directory, and any folder containing it. | |
| LOCAL_IMAGE_CONVERT_NO_HEIC | No | Kill-switch: disable HEIC/HEIF decoding (set to 1 to disable). | |
| LOCAL_IMAGE_CONVERT_MAX_INPUT_MB | No | Largest input file in MB (default 100). | |
| LOCAL_IMAGE_CONVERT_MAX_MEGAPIXELS | No | Largest decoded image in megapixels (default 100). | |
| LOCAL_IMAGE_CONVERT_MAX_BATCH_FILES | No | Most files in one batch_convert call (default 200). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| convert_imageA | Convert one local image (JPEG, PNG, WebP, AVIF, GIF, TIFF, HEIC/HEIF) to jpeg, png, webp or avif. Runs entirely on this machine; nothing is uploaded. Paths are relative to the allowed root (/app). Writes a new file and never overwrites existing ones. Returns the output path and sizes. |
| batch_convertA | Convert several local images at once, from a list of paths and/or a directory (non-recursive). Writes the results as separate files or as one .zip archive into outputDir. Continues past bad files and reports each error. Runs entirely on this machine. Limit: 200 files per call. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
convert_image and batch_convert are clearly distinguished by single-file vs multi-file operation. The descriptions make the boundary explicit (one image vs list/directory, separate files vs zip).
Both names use snake_case and follow an action_object pattern (convert_image, batch_convert). The deviation is minor: 'batch' is a qualifier rather than a strict verb_noun parallel, but it reads naturally.
With only 2 tools the surface is thin, but for a focused image conversion server the single vs batch split is a reasonable minimal scope. It is borderline rather than clearly under-provisioned.
Core conversion is covered, but there is no tool to inspect image metadata, validate paths, or list supported formats/roots. For a local conversion domain, basic CRUD-style operations beyond convert are absent, leaving some discovery dead ends.