local-image-convert-mcp
Related Servers
Alternatives to local-image-convert-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceLocal image tools for agents: convert, resize, compress, crop, rotate, blur, watermark, strip metadata, merge and thumbnails. Reads iPhone HEIC, takes file paths instead of base64, and uploads nothing.10MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to process images locally via file paths—converting, resizing, removing backgrounds, smart cropping, upscaling, reading or stripping metadata, and batch processing—without files ever leaving the device.MIT
- AlicenseBqualityBmaintenanceEnables AI assistants to inspect, convert, resize, crop, merge, extract and OCR local images, PDFs, audio and video entirely on the user's machine. Modules can be toggled individually, and all operations stay within a sandboxed working folder with atomic writes and no data sent anywhere.21MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to remove backgrounds, compress, resize, crop, AI-upscale, and strip metadata from images entirely on the local computer, so files never leave it.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to inspect, convert, and optimize image assets within project repositories while preserving transparency, sandboxing operations to the workspace root, stripping metadata with verifiable clean certificates, and reverting conversions through a local journal.MIT
- AlicenseNot gradedqualityCmaintenanceEnables an AI agent to inspect images, resize and compress them to size budgets, strip EXIF/GPS metadata, generate thumbnails, and safely batch-process files inside a directory sandbox.MIT
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.