# ComfyUI Ships Official Agent Tooling — and a Community Project Bows Out Gracefully

- Published: 15 September 2026
- Updated: 15 September 2026
- Author: RenderBob team
- Category: News
- Canonical: https://renderbob.io/blog/comfyui-official-agent-mcp-tooling

Comfy-Org has shipped official Comfy Agent and Comfy MCP tooling. A widely used community MCP server is archiving itself in response on 9 October 2026.

Comfy-Org has shipped official agent and MCP (Model Context Protocol) tooling, Comfy Agent and Comfy MCP, built and supported directly by the core team, with what the ecosystem itself describes as deeper integration than a community project can match. In a rare and useful move, one of the most widely used community alternatives, comfyui-mcp, is responding by archiving itself: no new features, fixes, or dependency updates, with the repository and its Discord community going fully read-only on 9 October 2026, left as a searchable archive.

This is a healthy pattern in open-source ecosystems, and it is relatively rare. The community project's own announcement is direct: if you are looking for an MCP server or AI agent for ComfyUI, use the official tooling now that it exists. Rather than competing indefinitely with a better-resourced official alternative, or quietly going unmaintained and misleading users who do not notice, the maintainer chose to say so plainly and point people at the better-supported path.

For agentic ComfyUI workflows, the pattern covered earlier on this blog with ComfyUI-Copilot and the broader agentic-graph trend, the practical effect is consolidation around a single, better-supported foundation. The community tool being retired had a broad feature set worth recording for what it demonstrated the category could do: 178 tools, 36 AI skills, 55 installer packs, the ability to run on any LLM including offline local models via Ollama with no network at all, and support for local, LAN, VPS or Comfy Cloud deployment from one configuration. Whether the new official tooling matches all of that breadth immediately or grows into it over time is worth watching. The direction, official, core-team-supported agent tooling as the default path, is the more important signal for a studio deciding what to standardise on.

If you have adopted comfyui-mcp or a similar community agent layer, start planning a migration to the official tooling before the October archive date, and treat this as the expected direction rather than a one-off. Official, core-team-maintained tooling carries a different risk and support profile than a community project, however excellent, and a studio's standard toolkit should lean toward the officially supported option once one exists and is mature, reserving community tools for the genuine gaps official tooling has not filled yet.