Skip to main content
Glama
Sign In
atiquefiroz

squoosh-mcp

by atiquefiroz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to squoosh-mcp

No user-submitted related servers found.

    Related Servers

    • obrobka-mcp

      ThatHunky
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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

    • ruah

      0-big
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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

    • SammaPix

      samma1997
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to run real image and PDF processing remotely — compressing, converting, resizing, cropping, watermarking, and chaining multiple operations in a single call — with no local install and zero-retention handling.
      8
      MIT

    • LazyRoom MCP Server

      adit-0132
      A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to drive a full photo-editing engine through validated, non-destructive operations — exposure and colour grading, effects, geometry, text/watermarks, style matching from a reference image, natural-language looks, and batch processing over folders. Originals stay untouched, edits live in an open JSON project format, and everything runs locally without network access unless opted in.
      27
      Apache 2.0
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A4.2/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: read-only inspection (analyze_images), mutation (optimize_images), async job control (get_job, cancel_job), and quality verification (compare_images). The get_job/cancel_job pair targets the same job resource but differs cleanly by action (wait/read vs stop). No plausible misselection risk.

    Naming Consistency5/5

    All five tools follow a consistent snake_case verb_noun pattern: analyze_images, optimize_images, get_job, cancel_job, compare_images. Even the resource-oriented job tools fit the same verb-first convention, with no style mixing.

    Tool Count5/5

    Five tools is well-scoped for an image optimization server: inspection, encoding, and verification are all explicit, and get_job/cancel_job exist because optimize_images can return a long-running jobId. Nothing feels padded or missing.

    Completeness4/5

    The analyze → optimize → verify → manage-job lifecycle is covered, including dryRun preview, per-policy formats, resize/srcset/crop, and SSIMULACRA 2 checking. Minor gaps: no tool to list/discover outstanding jobs (a jobId is only obtainable from a running optimize call) and no way to clean up or roll back written outputs.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources