ComfyUI MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow maintenance status and local image-workflow compatibility as releases return

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Driving local or remote ComfyUI workflows from an AI assistant

What we know

MCP server exposing a broad ComfyUI tool set for image generation, workflow authoring, models, custom nodes and server control.

Maintenance / activity evidence

Observed Oct 1, 2026 (UTC)Merge pull request 2962 from artokun/codex/fork-maintenance-fixes

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Activity source · commits ↗Activity source · releases ↗

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Broad ComfyUI workflow/server capabilities. Writes: Generate files; Modify workflows; Install/manage nodes/models depending on tools.
Deployment-specific for remote use.
Sensitive access: Prompts, Images, Models/workflows

The tool surface can change ComfyUI configuration and create files; local and remote modes need different controls.

Security source · repository notice ↗

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

763 repository stars

Stars observed Sep 25, 2026.

Preserve any already-reviewed adoption metrics in MCP100. Batch 4 did not refresh package downloads because the package-stats provider had insufficient credits.

All limitations / Review context

Which ComfyUI workflows and provider modes remain supported after maintenance resumed?

The bounded assessment reviewed the official README, repository notices, security policy path, and security page for known material public-tracking blockers. No such blocker was identified. This is a public-tracking assessment, not an installation safety certification.

The tool surface can change ComfyUI configuration and create files; local and remote modes need different controls.
Broad ComfyUI workflow/server capabilities.
Deployment-specific for remote use.
Prompts, workflows and generated media may be sent to the configured ComfyUI instance.
Reviewed write actions: Generate files; Modify workflows; Install/manage nodes/models depending on tools
Sensitive access: Prompts, Images, Models/workflows
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
A project-specific SECURITY.md policy was not available at the fetched official path; the review remains limited to published repository notices.
No installation, runtime, client matrix, or complete tool-contract audit was performed in this review.
The fetched official SECURITY.md path returned HTTP 404; it was not treated as positive evidence.
Requires a reachable ComfyUI instance.
Remote/tunnel deployments have a materially different authentication/network boundary from local stdio use.

Original activity observations

2026-10-01T23:38:00Z: Merge pull request 2962 from artokun/codex/fork-maintenance-fixes

Technical identity

github.com/artokun/comfyui-mcp

Exact implementation source: https://github.com/artokun/comfyui-mcp ↗
Reviewed resource type: MCP Server
Repository identity: artokun/comfyui-mcp
Package identity: npm:comfyui-mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 6, 2026

GitHub repository ↗
artokun/comfyui-mcp
Recorded repository material and project history.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Claude Code

Publisher instructions with a documented client setup path.

Source evidence observed Oct 12, 2026.

Additional setup details required — see the specific gaps below.

Warning

Publisher README calls this a Claude Code configuration example; no separate Claude Desktop publisher attribution is asserted.
ComfyUI must be installed and running to use local workflows.
Publisher-specific exact credential-revocation procedure not established; use the issuing provider controls only if credentials actually exist.
Credential revocation is external-provider-specific or not documented in examined official project Setup/README; do not assert exact revocation CLI.
This command may start a stdio MCP server rather than registering it; show the publisher client config alongside it, not as a standalone complete integration step.
Replace the supplied credential/path placeholders privately; use only the named configuration schema.
Official repo README declares this community ComfyUI project no longer maintained; publisher directs new installations to official Comfy-Org tooling.

Install / connect
Publisher instructions
Legacy community project announced end of maintenance. Existing users can follow archived install instructions, but for new installations prefer the official Comfy-Org tooling. Preserve historical compatibility rather than claiming actively maintained support.
npx -y comfyui-mcp
Configure / authenticate
Publisher instructions
Use the dedicated official llms-install.md guide to choose local, remote or Comfy Cloud, then configure ComfyUI endpoint and any needed tokens privately. Models/downloads/workflows can perform heavy actions; avoid executing generation during basic connectivity checks.
Advanced configuration · claude code settings json publisher example
{ "mcpServers": { "comfyui": { "args": [ "-y", "comfyui-mcp" ], "command": "npx", "env": { "CIVITAI_API_TOKEN": "" } } } }
Check connection
Suggested check
Confirm both ComfyUI service startup and comfyui-mcp tool discovery. Avoid generation, model downloads and custom-node changes as mere connectivity tests. Client registration check: `claude mcp get comfyui` (checks registration; inspect tools/read-only calls separately to verify authenticated service access).
Remove / uninstall / revoke
MCP100 setup guide
Remove the matching MCP configuration from the client. This does not uninstall the local package or revoke provider credentials. Client disconnect (claude-code, only if registered using the name `comfyui`): `claude mcp remove comfyui`. This unregisters the client entry; it does not uninstall packages or revoke remote service credentials.
claude mcp remove comfyui

Official Documentation & Sources

What it does

MCP server exposing a broad ComfyUI tool set for image generation, workflow authoring, models, custom nodes and server control.

Capability: Design & Creative
Resource type: MCP Server
Best fit: Driving local or remote ComfyUI workflows from an AI assistant

Representative uses

Generate images
Run/edit workflows
Manage models/custom nodes
Inspect/control ComfyUI

Limitations

Requires a reachable ComfyUI instance.
Remote/tunnel deployments have a materially different authentication/network boundary from local stdio use.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Deployment-specific for remote use.
Permissions: Broad ComfyUI workflow/server capabilities.
Data handling: Prompts, workflows and generated media may be sent to the configured ComfyUI instance.
Cost: free
Risk and cautions: The tool surface can change ComfyUI configuration and create files; local and remote modes need different controls.

Access scope and cautions

Write actions: Generate files Modify workflows Install/manage nodes/models depending on tools
Sensitive access: Prompts Images Models/workflows
Risk level: high

FAQ

Based on reviewed evidence as of 2026-10-06. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Generate images; Run/edit workflows; Manage models/custom nodes; Inspect/control ComfyUI.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx comfyui-mcp. Recorded transport: stdio, streamable_http. Prerequisites: Node.js 22+; ComfyUI. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Local mode typically uses local ComfyUI; remote mode depends on deployment credentials.

Can it modify data or perform write operations?

Documented write actions include: Generate files; Modify workflows; Install/manage nodes/models depending on tools. Recorded permission boundary: Broad ComfyUI workflow/server capabilities.

What data-handling boundary should I consider?

Prompts, workflows and generated media may be sent to the configured ComfyUI instance. Recorded sensitive-access context: Prompts; Images; Models/workflows.

What limitations and risks should I check before use?

The tool surface can change ComfyUI configuration and create files; local and remote modes need different controls. Requires a reachable ComfyUI instance. Remote/tunnel deployments have a materially different authentication/network boundary from local stdio use. A project-specific SECURITY.md policy was not available at the fetched official path; the review remains limited to published repository notices.

Is this an official MCP?

artokun is listed as Community implementation in MCP100’s current evidence.