tinypng-mcp-server
Related Servers
Alternatives to tinypng-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenance🧙🏻 Integrated TinyPNG MCP server, quickly use TinyPNG through LLMs.311 npmApache 2.0
- AlicenseAqualityAmaintenanceMCP server for tinify.ai image optimization. AI-powered upscaling, resizing/cropping, compression, and SEO filename & alt text generation — all in one tool.5203 npm2MIT
- AlicenseCqualityDmaintenanceImage Tools MCP is a Model Context Protocol (MCP) service that retrieves image dimensions and compresses images from URLs and local files using the TinyPNG API. It supports converting images to formats like webp, jpeg/jpg, and png, providing detailed information on width, height, type, and compressi223 npm8MIT
- AlicenseAqualityAmaintenanceCompress, resize, crop and convert images via tinify.dev571 npmMIT
- AlicenseNot gradedqualityAmaintenanceMCP implementation for connecting to the Mochify image processing API to convert, compress and resize images.1MIT
- AlicenseCqualityCmaintenanceMCP server for local compression of various image formats110 npm34MIT
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: compress_local_image handles local files, compress_remote_image handles URLs, and resize_image performs a different operation entirely. There is no overlap or ambiguity between these three functions.
All tools follow a consistent verb_noun pattern with snake_case naming: compress_local_image, compress_remote_image, and resize_image. The naming is predictable and uniform throughout the set.
With 3 tools, this server is well-scoped for its purpose of image processing with TinyPNG. Each tool earns its place by covering distinct aspects: local compression, remote compression, and resizing. This is an appropriate number for the domain.
The tool surface covers the core operations for image compression and resizing with TinyPNG, handling both local and remote sources. A minor gap might be the lack of a tool for batch processing or metadata retrieval, but agents can work around this with sequential calls.