Comfy Local MCP
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Comfy Local MCPrun the 'product-shot' workflow"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Comfy Local MCP
Windows-native MCP server for a local ComfyUI portable package. It talks to
ComfyUI over its loopback HTTP API and runs with the portable package's own
python_embeded\python.exe; no virtual environment is required.
Portable layout
The MCP package is expected to be placed next to the portable package folders:
ComfyUI_windows_portable\
ComfyUI\
python_embeded\
comfy-local-mcp\The installer also accepts an explicit -PortableRoot when the MCP package is
stored elsewhere.
Related MCP server: ComfyUI MCP
Install
From PowerShell, run install.ps1 in the extracted package directory:
.\install.ps1 -PortableRoot "F:\ComfyUI_windows_portable" -RegisterCodexThe installer:
uses
ComfyUI\..\python_embeded\python.exedirectly;installs the pinned MCP dependency into this package's
vendordirectory;copies bundled API-format workflows into
ComfyUI\user\default\workflows;uses
ComfyUI\outputas the output directory;optionally registers the MCP server with Codex.
No files are installed into ComfyUI's python_embeded\Lib\site-packages.
Runtime configuration
COMFYUI_URL: loopback ComfyUI URL, defaulthttp://127.0.0.1:8188.COMFY_PORTABLE_ROOT: portable root containing siblingComfyUIandpython_embededdirectories.COMFYUI_ROOT: optional explicit ComfyUI directory.COMFY_MCP_WORKFLOW_ROOT: defaults toComfyUI\user\default\workflows.COMFY_MCP_OUTPUT_ROOT: defaults toComfyUI\output.COMFY_MCP_ALLOWED_ROOTS: semicolon-separated workflow/output roots.
The MCP tools list_workflows and save_workflow operate in the configured
workflow directory. validate_workflow and run_workflow accept either an
absolute path inside that directory or a workflow filename.
Build a Release
From the repository root:
.\tools\comfy_local_mcp\build_release.ps1 -Version "0.1.0"The generated archive is written to dist\comfy-local-mcp-0.1.0.zip.
Notes
ComfyUI must be running before calling server_info, validate_workflow, or
run_workflow. Models and custom nodes remain customer-local; the MCP package
does not download or share model weights.
This server cannot be deployed
Maintenance
Related MCP Connectors
MCP server for OpenAI API (chat completions, image generation, embeddings) via AceDataCloud
MCP server for Producer/Riffusion AI music generation
Focused MCP server for OpenAI image/audio generation (v2.0.0). Wraps endpoints via HAPI CLI.
MCP server for Qwen Image 3 AI image generation
Related MCP Servers
- AlicenseAqualityDmaintenanceMCP server for ComfyUI — text-to-image, variations, img2img refine, upscale, image proxy, and workflow runner.1584 npm2MIT
- FlicenseAqualityDmaintenanceMinimal MCP server that wraps ComfyUI HTTP routes enabling LLM clients to inspect server status, models, features, node metadata, submit workflows, manage queue/history, interrupt runs, and upload images.11-
- AlicenseNot gradedqualityDmaintenanceLocal-first MCP server for controlling a loopback ComfyUI instance from same-machine or authenticated LAN clients.MIT
- FlicenseNot gradedqualityDmaintenanceMCP server exposing a local (or LAN) ComfyUI instance's HTTP API as tools, so an LLM client can queue generations, inspect the queue/history, upload reference images, browse installed models/nodes, and pull back generated images.-