fitfilesize-mcp
Related Servers
Alternatives to fitfilesize-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to analyze, compress, and verify PDFs while preserving text, vectors, and document structure, with configurable presets and target-size limits.1MIT

Formatika MCPofficial
AlicenseAqualityBmaintenanceProvides tools to convert, resize, compress, crop, and rotate files (images, audio, video, PDF, archives, and more) through formatika.app, processing files locally and preserving existing files.3836 npmMIT- AlicenseBqualityCmaintenanceEnables AI agents to convert documents, images, and data files across 50+ format pairs and to run PDF/image operations such as merge, split, compress, rotate, protect, unlock, extract text, and resize or compress images. Files are passed URL-in and returned URL-out (or saved locally in stdio mode), with tools for checking credits and generating Stripe checkout or billing-portal links.1834 PyPIMIT
- AlicenseAqualityBmaintenanceConverts Office documents, images, and e-books to PDF and transforms PDFs by merging, splitting, rotating, numbering, watermarking, compressing, protecting, or unlocking them, plus PDF-to-Word and PDF-to-image conversion, all driven by natural language. Files stay on the user's computer apart from the conversion itself, which runs on EU-hosted servers in France.121355 npmMIT
- AlicenseAqualityBmaintenanceCompress, merge, split, OCR and convert PDFs (Word, Office, images, webpages) on local files, plus password protect and unlock, through the Papyrio API. Works without a key on a free guest tier; an optional RapidAPI key raises the limit.12598 npm1MIT
- AlicenseAqualityBmaintenanceA local-first PDF tool for merging, splitting, rotating, watermarking, Bates-numbering, cleaning metadata, and counting pages — all operations happen on your machine with no network transmission.1546 npm1MIT
TDQS
Scored across 2 tools
The two tools have completely distinct purposes: fit_file performs the compression and list_forms only enumerates presets. There is no plausible scenario where an agent would confuse which one to call, and the descriptions even state the relationship (pass a form id from list_forms into fit_file).
Both names use the same snake_case verb_noun convention (fit_file, list_forms) with no mixed styles or casing deviations. The pattern is predictable and readable even for only two tools.
Two tools is minimal, but this is a deliberately narrow single-purpose server (compress a file to a size limit), and each tool clearly earns its place. It is slightly thin in that a size-estimate or verification operation could reasonably exist, but nothing feels padded or missing for the core job.
The core lifecycle is covered: enumerate presets, then compress one or many files by limit or form, with format and output-location behavior documented. Minor gaps exist, such as no way to preview an estimated result size before compressing, no control over the output path, and no programmatic format list.