Skip to main content
Glama
tsyecommercialdesigner-cloud

Zhenzhen Image MCP

by tsyecommercialdesigner-cloud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Zhenzhen Image MCP

No user-submitted related servers found.

    Related Servers

    • gpt-image-mcp

      zK0G0w
      A
      license
      A
      quality
      B
      maintenance
      Local stdio MCP service that calls GPT Image API to generate images from text, edit images with references or masks, and save images locally while returning absolute paths and file URIs.
      3
      37 npm
      1
      MIT

    • Fatima Image Studio MCP Server

      hassanxs
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to generate and manage bulk AI images locally through the app's engine, including batches, reference images, LoRAs, upscaling, and OpenAI-compatible API operations. It connects MCP clients such as Claude Code, Codex, Antigravity, and Hermes to a self-hosted Windows image-generation workflow without cloud accounts.
      MIT

    • SXS Control

      wenmingsun60-bit
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables local AI clients on Windows to automate desktop and system tasks via MCP stdio, CLI, or optional localhost HTTP, including screenshots, mouse and keyboard input, files, processes, registry, and accessibility-tree window interactions, with local-only execution and no cloud fallback.
      MIT

    • imaginate-mcp

      pinkpixel-dev
      A
      license
      A
      quality
      B
      maintenance
      Generates and edits images using OpenAI GPT Image or Google Gemini models, saving every result to disk and returning local file paths so AI assistants can continue working with the images. It enables prompt-based image creation, editing, inpainting, multi-image composition, and model listing through MCP tools.
      1
      9 npm
      1
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 12 tools

    Disambiguation3/5

    The set contains several near-pairs: generate_image vs submit_image_generation, edit_image vs submit_image_edit, submit_image_batch vs run_image_batch, and get_image_task vs get_batch_image_task vs get_image_batch. Descriptions clarify sync vs async and local vs provider state, but an agent can still easily misselect among similarly named tools.

    Naming Consistency3/5

    All names are snake_case with verb-first structure, but the conventions vary between verb_resource_action (submit_image_batch), verb_resource (generate_image), and inconsistent ordering such as get_image_batch vs get_batch_image_task. The patterns are readable but not predictable enough to prevent confusion.

    Tool Count4/5

    Twelve tools is a reasonable scope for covering sync/async generation, editing, batch execution, querying, waiting, and downloading. Some sync/async/batch variants feel redundant, but each mode can earn its place.

    Completeness4/5

    The surface covers generation, editing, batch operations, task polling, download validation, and model guidance. Minor gaps exist around cancellation or management of async jobs, but core image workflows are covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources