compress_image_from_url
Compress a single image from URL using TinyPNG API (only supports image files, not folders)
LABSCO 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
USE CASES
01
Shrinking an asset before it lands in the repository
Read the local file's size, then run it through TinyPNG compression one file at a time.
02
Checking a remote image before you adopt it
Read the size of the image behind the URL, and compress it from that URL if it is worth keeping.
03
Getting the exported images out of a Figma file
Pull the images from the Figma API in the same session that writes the markup they belong to.
5 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
compress_local_image
Compress a single local image file using TinyPNG API (only supports image files, not folders)
get_figma_images
Get images from Figma API
get_image_size
Get the size of an image from URL
get_local_image_size
Get the size of a local image
BEFORE YOU INSTALL
What to know first
Tools you get
5 tools when we connected. With no keys set, only get_image_size and get_local_image_size appear; TINIFY_API_KEY adds the two compress tools and FIGMA_API_TOKEN adds get_figma_images, which the documentation calls figma.
Requires
- npx on PATH
- TINIFY_API_KEY in your environment
- FIGMA_API_TOKEN in your environment
Where it runs
The documented client runs the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 5 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx image-tools-mcpMCP Clients
Any MCP client
ANY MCP CLIENT · JSON
{
"mcpServers": {
"image-tools": {
"command": "npx",
"args": [
"image-tools-mcp"
],
"env": {
"TINIFY_API_KEY": "<YOUR_TINIFY_API_KEY>",
"FIGMA_API_TOKEN": "<YOUR_FIGMA_API_TOKEN>"
}
}
}
}
