artokun/comfyui-mcp: README-based editorial guide
A guide grounded in the README, repository metadata, and license for installing and checking artokun/comfyui-mcp.
Project scope
artokun/comfyui-mcp describes itself in the README as "Local-first, agent-native control plane for ComfyUI , MCP server + sidebar agent that generates images, video & audio, authors and runs workflows, and edits your live graph in natural language on ANY LLM (Claude, ChatGPT, Gemini, offline". This article keeps to facts that can be checked in the repository. Stars, forks, and promotional badges are signals of attention, not proof of quality. Under "comfyui-mcp , drive ComfyUI with ANY LLM", the README says: The local-first, agent-native control plane for ComfyUI scores them all on real ComfyUI tasks so you know exactly what your model can do. One config targets local installs, LAN, VPS, or Comfy Cloud.. That establishes the project's stated boundary, not a production test.
Suitable use cases
The README's "Configuration" section gives a useful starting point for deciding whether the project fits: Panel users: the API Keys card (▾ menu next to "connected") , stored in /.comfyui-mcp/panel-secrets.json, applied immediately, no restart.. If that problem is not yours, popularity is a poor reason to adopt it. Project names, commands, and component names are kept as written so a reader can return to the primary source without guessing at terminology. Another checkable README item is: CodexBackend , OpenAI Codex over the codex app-server JSON-RPC. It can shape a first test, but it does not replace testing in the intended environment.
How it works
The operating model is spread across sections such as "comfyui-mcp , drive ComfyUI with ANY LLM". The source evidence includes: Stuck or have a question? Join the Discord , help, model tips, and release announcements.. This article does not turn missing architecture, performance, or security details into claims. A real deployment still needs a look at the repository layout, configuration files, and release history.
Installation and first run
Start installation from the README's documented entry point. A command that can be checked in the source is: # View local stats from the CLI npm run generations:stats When the README contains no runnable command, this article does not invent one. Open its "Quick Start" section and confirm system dependencies, default ports, and first-run initialization before using a public server.