Skip to main content
Glama
yutianxiao6

ComfyUI MCP

by yutianxiao6
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to ComfyUI MCP

No user-submitted related servers found.

    Related Servers

    • comfyui-mcp

      bernardogv
      A
      license
      A
      quality
      B
      maintenance
      MCP server that lets AI agents drive a remote ComfyUI instance end-to-end, including queueing workflows, viewing outputs, downloading models, and authoring graphs via ComfyScript.
      16
      43,607 npm
      MIT

    • comfy-draftsman

      EnragedAntelope
      A
      license
      A
      quality
      A
      maintenance
      The MCP server that drafts ComfyUI workflows a human can actually read. It lets coding agents build, repair, port, validate, and run ComfyUI workflows against your own ComfyUI instance, delivering clean, organized, fully-labeled workflows.
      29
      2
      MIT

    • comfy-mcp

      cuzelac
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that enables AI agents to control a local ComfyUI instance for image generation, allowing workflow understanding, parameter modification, execution, and model discovery.
      23 npm
      3
      Apache 2.0

    • local-comfyui-mcp

      pytraveler
      A
      license
      A
      quality
      A
      maintenance
      An MCP server that integrates with a local ComfyUI, allowing assistants to list and run workflows, monitor progress, and view results, as well as read and edit the live workflow canvas via an optional bridge node.
      64
      11
      GPL 3.0

    • comfyui-mcp

      KerbalTheGathering
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server exposing a local (or LAN) ComfyUI instance's HTTP API as tools, so an LLM client can queue generations, inspect the queue/history, upload reference images, browse installed models/nodes, and pull back generated images.
      -
    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.5/5.0

    Scored across 23 tools

    Disambiguation5/5

    Each tool targets a unique resource and action, from health checks to node introspection, workflow editing, execution, and queue control. Even closely related tools like add_node and set_input have clear boundaries, leaving no ambiguity.

    Naming Consistency5/5

    All tools follow a consistent comfyui_verb_noun snake_case pattern. Verbs like list, get, create, add, remove, connect, disconnect, and validate are consistently used, making the toolset predictable and easy to navigate.

    Tool Count4/5

    At 23 tools, this is on the heavy side, but the breadth is justified by the complex domain of ComfyUI workflow management. Each tool serves a distinct purpose, and the count remains reasonable given the need to cover discovery, editing, validation, execution, and file I/O.

    Completeness4/5

    The toolset covers the full lifecycle of workflow management, including creation, importing, editing, validation, running, queue inspection, and output retrieval. Minor gaps exist, such as the lack of a delete_workflow tool or a list_runs tool, but these are not critical for core usage.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources