Back to Browse

Comfyui Light MCP Server

AI & MLLow Risk8.0MCP RegistryLocal
Free

Server data from the Official MCP Registry

Workflow-first, Batch-native, Context-light.

About

Workflow-first, Batch-native, Context-light.

Security Report

8.0
Low Risk8.0Low Risk

Valid MCP server (4 strong, 3 medium validity signals). 3 known CVEs in dependencies (0 critical, 1 high severity) Imported from the Official MCP Registry. 1 finding(s) downgraded by scanner intelligence.

9 files analyzed · 4 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

file_system

Check that this permission is expected for this type of plugin.

env_vars

Check that this permission is expected for this type of plugin.

database

Check that this permission is expected for this type of plugin.

What You'll Need

Set these up before or after installing:

Required installation choice: your trusted running ComfyUI HTTP(S) endpoint. No credentials, query or fragment.Optional

Environment variable: COMFYUI_URL

Required absolute existing directory containing your reviewed workflow API JSON and manifest pairs.Optional

Environment variable: WORKFLOWS_DIR

Required absolute writable SQLite state directory. Use a separate directory per MCP process.Optional

Environment variable: DATA_DIR

Required absolute writable output/download/index directory.Optional

Environment variable: OUTPUT_DIR

Application default: true. Download outputs on completion; false defers downloads to result queries.Optional

Environment variable: AUTO_SAVE_OUTPUTS

Application default: 1. Integer 1-64; includes uncertain submissions.Optional

Environment variable: MAX_IN_FLIGHT

Application default: 1. Integer 1-64, no greater than MAX_IN_FLIGHT.Optional

Environment variable: MAX_QUEUED_JOBS

Application default: 600000. Integer 10000-86400000 milliseconds.Optional

Environment variable: JOB_TIMEOUT_MS

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "comfyui-light-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "comfyui-light-mcp@0.3.0-rc.2"
      ],
      "env": {
        "DATA_DIR": "your-data-dir-here",
        "OUTPUT_DIR": "your-output-dir-here",
        "COMFYUI_URL": "your-comfyui-url-here",
        "MAX_IN_FLIGHT": "your-max-in-flight-here",
        "WORKFLOWS_DIR": "your-workflows-dir-here",
        "JOB_TIMEOUT_MS": "your-job-timeout-ms-here",
        "MAX_QUEUED_JOBS": "your-max-queued-jobs-here",
        "AUTO_SAVE_OUTPUTS": "your-auto-save-outputs-here"
      }
    }
  }
}

Some servers take additional arguments. See the repository for details.

Documentation

View on GitHub

From the project's GitHub README.

ComfyUI Light MCP

简体中文 · User guide · Magpie setup · MIT · Prerelease 0.3.0-rc.2

A local stdio MCP server that lets an AI client run ComfyUI workflows you have already reviewed.

Product direction

Workflow-first, Batch-native, Context-light.

  • Workflow-first: export a workflow from ComfyUI in API format once, and write a manifest that whitelists the parameters a client may change. Each call sends only those parameters, not the whole graph.
  • Batch-native: one call submits up to 200 labeled runs, with idempotency keys, SQLite persistence and conservative recovery after interruption.
  • Context-light: only four tools, list_workflows, run_workflow, get_batch, get_result. Tools return summaries and paginated status; batch results can be written to a local JSONL index without returning image data into the conversation.

Requires Windows 11 x64 and Node.js 22.12+. ComfyUI must be installed and running separately. This server does not install ComfyUI, custom nodes or models.

Differences from the official Comfy MCP

Comfy Org's official Comfy MCP aims at driving ComfyUI from AI agents in general: it is Python-based (via comfy-cli), exposes around 40 tools, and can search the official template gallery, fetch and modify workflow graphs, validate them against the local install, and more; a hosted Comfy Cloud variant also exists.

What this project lacks next to that is deliberate:

  • No workflow editing through MCP. A workflow is a plain JSON file in WORKFLOWS_DIR, paired with its manifest. Agents can use their file tools to maintain the pair. Changes are detected on the next list, run or dry-run call and by the scheduler. Invalid edits block new execution instead of falling back to an older graph; pending jobs pause if their saved workflow fingerprint no longer matches.
  • A minimal MCP surface. Only what must pass through the server goes through MCP: submitting whitelisted parameters, scheduling batches, tracking state and collecting results. Template galleries, uploads and model management are out of scope; the workflow file remains an ordinary file the agent can edit.
Official Comfy MCPThis project
ScopeGeneral agent control of local (or cloud) ComfyUIRunning pre-approved local workflows only
Workflow sourceOfficial template gallery, fetched/composed/edited by the agentLocally exported API JSON + a manifest parameter whitelist
Tools~40 (search, compose, edit, validate…)4 (list / run / poll / fetch results)
Per callThe agent can send and modify full workflow graphsOnly whitelisted parameters are sent
Stack / licensePython + comfy-cli, AGPL-3.0 or commercialNode.js 22, MIT
PlatformCross-platformWindows 11 x64 only

The two overlap but are not substitutes: use the official server when the agent should compose and modify workflows through MCP tool calls; this project is a narrower option when workflows live as plain files — edited with the agent's own file tools — and MCP is used only to run them, including in batches.

Installation for AI agents

Follow these steps to install this server for your user. Target environment: Windows 11 x64, Node.js >= 22.12, ComfyUI already running (default http://127.0.0.1:8188).

  1. Clone or unpack the source, then in the checkout run:

    npm ci          # do not use --ignore-scripts; better-sqlite3 loads a native addon
    npm run build
    
  2. Add the server to the user's MCP client settings, replacing placeholder paths with real absolute paths and adjusting environment variables as needed:

    {
      "mcpServers": {
        "comfyui-light": {
          "command": "node",
          "args": ["C:/mcp/comfyui-light-mcp/dist/index.js"],
          "env": {
            "COMFYUI_URL": "http://127.0.0.1:8188",
            "WORKFLOWS_DIR": "C:/mcp/workflows",
            "DATA_DIR": "C:/mcp/data",
            "OUTPUT_DIR": "C:/mcp/output"
          }
        }
      }
    }
    
  3. Place workflow API JSON files and their *.manifest.json into WORKFLOWS_DIR. For a first check, copy both files from examples/ to that directory. Subsequent edits reload automatically; changing environment variables requires a server restart.

  4. Verify with list_workflows, then call run_workflow with {"workflow":"solid-color","dry_run":true,"params":{"color":255}}. Check errors, warnings and any unknown checks before running. Omit dry_run to generate the model-free example.

For manual configuration, launch node .../dist/index.js directly. The Magpie guide covers package-based startup. Stdout is reserved for the MCP protocol; a terminal launch simply waits for JSON-RPC input. For all configuration variables see config.env.example; for a minimal manifest see examples/.

See the user guide for local tarball installation, configuration, batch submission, result indexes, backups and recovery. Run one MCP process per database against a trusted local ComfyUI endpoint. This server has no backend authentication configuration. It does not guarantee token or cost savings. For development commands see CONTRIBUTING.md.

Reviews

No reviews yet

Be the first to review this server!