ComfyUI Light MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 319 installs a week from npm. Last commit 11 Nov 2026.
Workflow-first, Batch-native, Context-light.
What the code does
We read the source, 4 h ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const full = path.join(dir, file);
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add comfyui-light-mcp -e 'COMFYUI_URL=<COMFYUI_URL>' -e 'WORKFLOWS_DIR=<WORKFLOWS_DIR>' -e 'DATA_DIR=<DATA_DIR>' -e 'OUTPUT_DIR=<OUTPUT_DIR>' -- npx -y comfyui-light-mcp{
"mcpServers": {
"comfyui-light-mcp": {
"command": "npx",
"args": [
"-y",
"comfyui-light-mcp"
],
"env": {
"COMFYUI_URL": "<COMFYUI_URL>",
"DATA_DIR": "<DATA_DIR>",
"OUTPUT_DIR": "<OUTPUT_DIR>",
"WORKFLOWS_DIR": "<WORKFLOWS_DIR>"
}
}
}
}[mcp_servers.comfyui-light-mcp]
command = "npx"
args = ["-y", "comfyui-light-mcp"]
env = { COMFYUI_URL = "<COMFYUI_URL>", WORKFLOWS_DIR = "<WORKFLOWS_DIR>", DATA_DIR = "<DATA_DIR>", OUTPUT_DIR = "<OUTPUT_DIR>" }{
"mcpServers": {
"comfyui-light-mcp": {
"command": "npx",
"args": [
"-y",
"comfyui-light-mcp"
],
"env": {
"COMFYUI_URL": "<COMFYUI_URL>",
"DATA_DIR": "<DATA_DIR>",
"OUTPUT_DIR": "<OUTPUT_DIR>",
"WORKFLOWS_DIR": "<WORKFLOWS_DIR>"
}
}
}
}{
"servers": {
"comfyui-light-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"comfyui-light-mcp"
],
"env": {
"COMFYUI_URL": "<COMFYUI_URL>",
"DATA_DIR": "<DATA_DIR>",
"OUTPUT_DIR": "<OUTPUT_DIR>",
"WORKFLOWS_DIR": "<WORKFLOWS_DIR>"
}
}
}
}Put your own values in place of
<COMFYUI_URL> (Required installation choice: your trusted running ComfyUI HTTP(S) endpoint. No credentials, query or fragment), <WORKFLOWS_DIR> (Required absolute existing directory containing your reviewed workflow API JSON and manifest pairs), <DATA_DIR> (Required absolute writable SQLite state directory. Use a separate directory per MCP process), <OUTPUT_DIR> (Required absolute writable output/download/index directory).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
AUTO_SAVE_OUTPUTS (Application default: true. Download outputs on completion; false defers downloads to result queries), MAX_IN_FLIGHT (Application default: 1. Integer 1-64; includes uncertain submissions), MAX_QUEUED_JOBS (Application default: 1. Integer 1-64, no greater than MAX_IN_FLIGHT), JOB_TIMEOUT_MS (Application default: 600000. Integer 10000-86400000 milliseconds).
Alternatives to ComfyUI Light MCP
same job, measured the same wayWorkflow-native MCP server for safe Odoo Enterprise back-office operations
Compare-first local MCP sidecar for browser AI workflows.
The Figma MCP server brings Figma design context directly into your AI workflow.
Local-first privacy MCP server for sensitive AI workflows
MCP-first control plane for ComfyUI workflows with explicit approvals and no silent downloads.
MCP-first control plane for ComfyUI workflows with explicit approvals and no silent downloads.
MCP Server that transforms ComfyUI workflows into AI-callable tools for MCP Host
MCP-native workflow engine: teach agents your processes once, they execute them consistently.
ComfyUI Light MCP — questions
Answers built from our own checks of this server.