Summary
The check-and-shrink step before an asset lands in the repository happens in the same place as the commit.
Both compression tools state their own boundary: a single image file per call, with no folder mode, so a batch is the caller's loop rather than the server's. The size tools split by location rather than by format, one for a URL and one for a path. Figma is the odd one out: it has its own token and returns images out of a design file, where the rest work on an image you can already point at.
What it is
A small image-handling server covering size lookups, TinyPNG compression and image retrieval from the Figma API.
What you get
- Size of an image at a URL with get_image_size, or of one on disk with get_local_image_size.
- Compression through the TinyPNG API, for a remote file with compress_image_from_url and a local file with compress_local_image — one image file per call, not a folder.
- Images from the Figma API with get_figma_images.
Requirements
TINIFY_API_KEY and FIGMA_API_TOKEN in the environment. The compression tools call the TinyPNG API; get_figma_images calls the Figma API.
Setup effort
One command plus a key — npx image-tools-mcp, then supply credentials