Our grade: 4 checks
Based on public data, not a full audit. See how we grade. Something changed? Request a re-grade.
Community rating
- 5 1
- 4 5
- 3 10
- 2 3
- 1 0
Trust in production
- Trust it - 16%
- With caveats - 58%
- Wouldn't - 26%
53% would recommend this server
How reviewers scored it
- Setup & docs 3.3
- Auth experience 3.6
- Reliability 3.3
- Maintainer responsiveness 3.6
Why it got a C
A community MCP server for ComfyUI (MIT, TypeScript, npm comfyui-mcp 0.52.206, about 900 GitHub stars, written almost entirely by one developer). It reaches a local, LAN, VPS or Comfy Cloud install and can build, run and queue workflows for images, video and audio, edit the graph you have open, download models (from Civitai with an optional token), and install, update or remove custom node packs. An optional sidebar panel and a Claude Code plugin with skills come from the same author. The default stdio setup has no login, which is fine on your own machine; for the remote mode use --tunnel or set COMFYUI_MCP_HTTP_TOKEN so a token is required. Biggest deduction: the AI can install a custom node pack from any git URL, and custom nodes run their own Python on your machine, so set COMFYUI_MCP_TOOL_PRESET=safe unless you want it installing code.
How to connect
// ~/.claude/settings.json (README quick start)
{ "mcpServers": { "comfyui": { "command": "npx",
"args": ["-y", "comfyui-mcp"],
"env": { "CIVITAI_API_TOKEN": "" } } } }
Is ComfyUI MCP (artokun/comfyui-mcp) safe?
Is ComfyUI MCP (artokun/comfyui-mcp) safe to use?
ComfyUI MCP (artokun/comfyui-mcp) grades C (usable with care). Login is optional, so check that it is turned on in your setup. Upkeep is hard to verify (closed source or a single maintainer), so pin the version you tested. It can run model-controlled code or uses a plaintext remote connection, so run it isolated with no credentials.
Does ComfyUI MCP (artokun/comfyui-mcp) have known vulnerabilities?
Not in our current data: it has no open CVEs or advisories. We re-check as new ones are published.
Does ComfyUI MCP (artokun/comfyui-mcp) support authentication?
Optionally. It can run with a login, but it does not require one, so turn it on.
Alternatives in Workflow Automation
- A Make MCPOfficial hosted Make server that exposes your scenarios (and, on paid plans, management tools) to agents.
- A NeverApply MCP ServerOfficial hosted server to search and match jobs, tailor resumes, prep for interviews and apply to jobs you approve, with separate read, write and apply OAuth scopes.
- A Repostit MCP ServerOfficial hosted server to draft social posts and carousels, schedule or publish them to your connected accounts, set up cross-posting workflows and check delivery.
- A n8n MCP Server (instance-level)n8n's built-in MCP server. Lets an agent search, run, and (from 2.13) build workflows on your instance.
- B Zapier MCPOfficial hosted Zapier server that lets an agent run actions across thousands of connected apps.
Community reviews
Our team uses it every day
Tried it on a side project first, then rolled it out at work. Out of the box it runs without sign-in, so remember to enable auth before exposing it anywhere. Token setup is the fiddliest part, after that it is smooth.
Used for Connecting the agent to existing automations
- Setup & docs 4/5
- Auth experience 4/5
- Reliability 4/5
- Maintainer responsiveness 4/5
Fine once configured properly
Some tools are great, a couple feel half finished. Out of the box it runs without sign-in, so remember to enable auth before exposing it anywhere. It is community maintained, so I pin the version and read the changelog before upgrading. I will check back in a few releases.
Used for Scheduled reporting jobs
- Setup & docs 4/5
- Auth experience 3/5
- Reliability 3/5
- Maintainer responsiveness 5/5
Recommended it to two teams already
Started with it as an experiment, now it is a fixture. Auth is optional, which is convenient locally. I turned it on before sharing it with the team. Used a fine-grained token with short expiry and it works fine with that. Keep permissions tight and it is a good tool.
Used for Routing inbound requests
- Setup & docs 4/5
- Auth experience 4/5
- Reliability 4/5
- Maintainer responsiveness 3/5
Decent, not set-and-forget
Works well enough for what I need. It is community maintained, so I pin the version and read the changelog before upgrading. I run it with auth enabled. Without it I would not let it near anything shared. Recommended, with sensible guardrails.
Used for Scheduled reporting jobs
- Setup & docs 3/5
- Auth experience 3/5
- Reliability 3/5
- Maintainer responsiveness 4/5
Struggled to get it stable
It works in a demo, but things got shaky under real use. Updates land regularly, and nothing broke when I upgraded. Token setup is the fiddliest part, after that it is smooth. Auth is optional, which is convenient locally. I turned it on before sharing it with the team.
Used for Scheduled reporting jobs
- Setup & docs 2/5
- Auth experience 4/5
- Reliability 2/5
- Maintainer responsiveness 3/5
Trustworthy enough for real work
I use this almost daily. Out of the box it runs without sign-in, so remember to enable auth before exposing it anywhere. Used a fine-grained token with short expiry and it works fine with that.
Used for Glue between tools that have no direct integration
- Setup & docs 5/5
- Auth experience 4/5
- Reliability 5/5
- Maintainer responsiveness 3/5
Does the job, docs could be better
Good for experimenting, still deciding about production. Used a fine-grained token with short expiry and it works fine with that. Auth is optional, which is convenient locally. I turned it on before sharing it with the team. I would use it in prod, but only with a human approving writes.
Used for Triggering workflows from chat
- Setup & docs 2/5
- Auth experience 4/5
- Reliability 3/5
- Maintainer responsiveness 4/5
Good, but read the permissions first
Took longer to configure than I expected. Releases come often and the changelog is clear. I run it with auth enabled. Without it I would not let it near anything shared. Fine in production if you sandbox it.
Used for Glue between tools that have no direct integration
- Setup & docs 3/5
- Auth experience 4/5
- Reliability 3/5
- Maintainer responsiveness 5/5
Handy for dev, careful in prod
Good for experimenting, still deciding about production. It is community maintained, so I pin the version and read the changelog before upgrading. Nice that it supports both stdio and HTTP, I use stdio locally and HTTP for the shared agent. Auth is optional, which is convenient locally. I turned it on before sharing it with the team.
Used for Glue between tools that have no direct integration
- Setup & docs 4/5
- Auth experience 3/5
- Reliability 3/5
- Maintainer responsiveness 3/5
Surprisingly polished
Our agents call this dozens of times a day. Auth is optional, which is convenient locally. I turned it on before sharing it with the team. Easy recommendation.
Used for Ops tasks like provisioning accounts
- Setup & docs 4/5
- Auth experience 4/5
- Reliability 5/5
- Maintainer responsiveness 5/5
Capable but needs guardrails
It does the job, but it took some tweaking. Auth is optional, which is convenient locally. I turned it on before sharing it with the team. Token setup is the fiddliest part, after that it is smooth.
Used for Triggering workflows from chat
- Setup & docs 2/5
- Auth experience 3/5
- Reliability 4/5
- Maintainer responsiveness 4/5
Too much access for my comfort
Not what I expected from the description. I run it with auth enabled. Without it I would not let it near anything shared. Not something I would put in production yet.
Used for Routing inbound requests
- Setup & docs 2/5
- Auth experience 4/5
- Reliability 2/5
- Maintainer responsiveness 2/5
Promising, a bit raw
I like it, with reservations. It is community maintained, so I pin the version and read the changelog before upgrading. Fine in production if you sandbox it.
Used for Connecting the agent to existing automations
- Setup & docs 4/5
- Auth experience 3/5
- Reliability 3/5
- Maintainer responsiveness 4/5
Too many sharp edges
I wanted to like this one. Out of the box it runs without sign-in, so remember to enable auth before exposing it anywhere. Nice that it supports both stdio and HTTP, I use stdio locally and HTTP for the shared agent. I would use it in prod, but only with a human approving writes.
Used for Triggering workflows from chat
- Setup & docs 2/5
- Auth experience 4/5
- Reliability 2/5
- Maintainer responsiveness 2/5
Solid core, fiddly setup
Useful tool, though I would not hand it to a junior unsupervised. It is community maintained, so I pin the version and read the changelog before upgrading. You can tell it is actively maintained, the rough edges keep getting fixed. Keep permissions tight and it is a good tool.
Used for Triggering workflows from chat
- Setup & docs 2/5
- Auth experience 4/5
- Reliability 3/5
- Maintainer responsiveness 4/5
Good defaults, good docs
Installed it on a Friday, it was part of my workflow by Monday. Out of the box it runs without sign-in, so remember to enable auth before exposing it anywhere. Worth it, just do not skip the hardening steps.
Used for Routing inbound requests
- Setup & docs 4/5
- Auth experience 4/5
- Reliability 3/5
- Maintainer responsiveness 4/5
Saves me a context switch every hour
Clear tool names, sensible outputs, very few surprises. Used a fine-grained token with short expiry and it works fine with that.
Used for Ops tasks like provisioning accounts
- Setup & docs 5/5
- Auth experience 4/5
- Reliability 5/5
- Maintainer responsiveness 3/5
Mixed feelings after two weeks
Mostly reliable, with the odd timeout. Token setup is the fiddliest part, after that it is smooth. Auth is optional, which is convenient locally. I turned it on before sharing it with the team.
Used for Connecting the agent to existing automations
- Setup & docs 3/5
- Auth experience 3/5
- Reliability 3/5
- Maintainer responsiveness 4/5
OK for read-only work
Useful tool, though I would not hand it to a junior unsupervised. Out of the box it runs without sign-in, so remember to enable auth before exposing it anywhere.
Used for Ops tasks like provisioning accounts
- Setup & docs 3/5
- Auth experience 2/5
- Reliability 3/5
- Maintainer responsiveness 3/5
Write a review
Ran this server? Tell other teams how it went. You get one review per server. We email you a link to confirm it, then an editor checks it before it goes up. We never show your email.