Skip to main content
by artokun · September 9, 2026 · project · goodbye
Update — October 1, 2026: Limited maintenance has resumed for comfyui-mcp and the Agent Panel. The official built-in Comfy Agent is available on Cloud; its local panel is still forthcoming. We will provide verified critical fixes for our local panel and preserve provider choice, including offline models. Automatic issue reporting stays disabled. There is no October 9 shutdown commitment or broad feature roadmap. We will reassess support when the official local panel is publicly available. Official availability.

​
Original announcement — superseded by the update above

The following September announcement is retained as historical context. Its maintenance, reporting, and shutdown statements do not describe the current policy. This is the last post. comfyui-mcp and the ComfyUI Agent Panel are archived. No new features, no bug fixes, no dependency updates. Issues and pull requests are closed.

​
Why

ComfyUI now ships its own agent and MCP tooling — Comfy Agent and Comfy MCP — built and supported by the Comfy-Org team. It sits inside the product, with a level of integration a community project can’t match from the outside, and it is where the effort belongs. Comfy wanted to do their own thing, and that is the right call for ComfyUI users. That also settles the other half of the question. Keeping a project like this alive is support work — triaging reports, chasing regressions in someone else’s release cycle, keeping up with a frontend that moves every week — and open source is a thankless place to do it. It made sense while there was nothing else. With an official tool in the box, it doesn’t.

​
Use the official tooling

If you came here looking for an MCP server or an AI agent for ComfyUI, start there.

​
Fork it, remix it

The code stays public as a reference, MIT-licensed. If some part of it is useful to you — the tool surface, the installer packs, the skills, the panel — fork it and make it yours. I’d genuinely like to see what people build out of the pieces. Nothing here needs my permission, and nothing here is coming back to me as a pull request, so don’t wait on that.

​
What happens to the npm package and the registry node

  • npm (comfyui-mcp) stays published, unmaintained. It will keep working for as long as ComfyUI keeps the surfaces it depends on. As ComfyUI grows and changes, it will eventually just stop working — that is expected, and it will not be fixed. When it does, I’ll unpublish it.
  • The Comfy Registry node (comfyui-agent-panel) follows the same path: it stays listed until it breaks, and then the submission comes down.
  • report_issue and the report-bug skill in the final release are stubs. They file nothing and point you at the official tooling instead.

​
Custom work

Looking for a ComfyUI or generative-AI integration expert? I take on custom solutions — reach me by email at art.longbottom.jr@gmail.com or on LinkedIn.

​
Thanks

To everyone who used it, starred it, forked it, filed a report, or sent a patch: thank you. It was fun. It was a good run. 🚀