ComfyUI MCP Server
1. Overview
- A server implementation for integrating ComfyUI with MCP.
- ⚠️ IMPORTANT: This server requires a running ComfyUI server.
- You must either host your own ComfyUI server,
- or have access to an existing ComfyUI server address.
2. Debugging
2.1 ComfyUI Debugging
python src/test_comfyui.py
2.2 MCP Debugging
mcp dev src/server.py
3. Installation and Configuration
3.1 ComfyUI Configuration
-
Edit
src/.envto set ComfyUI host and port:COMFYUI_HOST=localhost COMFYUI_PORT=8188
3.2 Adding Custom Workflows
- To add new tools, place your workflow JSON files in the
workflowsdirectory and declare them as new tools in the system.
4. Built-in Tools
-
text_to_image
- Returns only the URL of the generated image.
- To get the actual image:
- Use the
download_imagetool, or - Access the URL directly in your browser.
- Use the
-
download_image
- Downloads images generated by other tools (like
text_to_image) using the image URL.
- Downloads images generated by other tools (like
-
run_workflow_with_file
-
Run a workflow by providing the path to a workflow JSON file.
# You should ask to agent like this. Run comfyui workflow with text_to_image.json -
example image of CursorAI
-
-
run_workflow_with_json
-
Run a workflow by providing the workflow JSON data directly.
# You should ask to agent like this. Run comfyui workflow with this { "3": { "inputs": { "seed": 156680208700286, "steps": 20, ... (workflow JSON example) }
-
5. How to Run
5.1 Using UV (Recommended)
-
Example
mcp.json:{ "mcpServers": { "comfyui": { "command": "uv", "args": [ "--directory", "PATH/MCP/comfyui", "run", "--with", "mcp", "--with", "websocket-client", "--with", "python-dotenv", "mcp", "run", "src/server.py:mcp" ] } } }
5.2 Using Docker
- Downloading images to a local folder with
download_imagemay be difficult since the Docker container does not share the host filesystem. - When using Docker, consider:
- Set
RETURN_URL=falsein.envto receive image data as bytes. - Set
COMFYUI_HOSTin.envto the appropriate address (e.g.,host.docker.internalor your server's IP). - Note: Large image payloads may exceed response limits when using binary data.
- Set
5.2.1 Build Docker Image
# First build image
docker image build -t mcp/comfyui .
{
"mcpServers": {
"comfyui": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-p",
"3001:3000",
"mcp/comfyui"
]
}
}
}
5.2.2 Using Existing Images
Also you can use prebuilt image.
{
"mcpServers": {
"comfyui": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-p",
"3001:3000",
"overseer66/mcp-comfyui"
]
}
}
}
5.2.3 Using SSE Transport
-
Run the SSE server with Docker:
docker run -i --rm -p 8001:8000 overseer66/mcp-comfyui-sse
-
Configure
mcp.json(change localhost to your IP or domain if needed):{ "mcpServers": { "comfyui": { "url": "http://localhost:8001/sse" } } }
NOTE: When adding new workflows as tools, you need to rebuild and redeploy the Docker images to make them available.
Metadata
Release files for iflow-mcp_overseer66_comfyui-mcp-server 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| iflow_mcp_overseer66_comfyui_mcp_server-0.1.0.tar.gz | 9.9 kB | Without provenance | Details for iflow_mcp_overseer66_comfyui_mcp_server-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| iflow_mcp_overseer66_comfyui_mcp_server-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for iflow_mcp_overseer66_comfyui_mcp_server-0.1.0-py3-none-any.whl |
Total release size: 21.2 kB
Release files / iflow_mcp_overseer66_comfyui_mcp_server-0.1.0.tar.gz
| Download URL | iflow_mcp_overseer66_comfyui_mcp_server-0.1.0.tar.gz |
|---|---|
| Size | 9.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2e41dbf02c360fdb87d4c539b24a861bf5ad1e5ebe4b57eeec81a27f0c537d7e
|
|
BLAKE2b-256 checksum How to use checksums |
321669d9b49048fca1bb203ffa09daf9392a10abadda04322b3cb72121813f7a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.28 {"installer":{"name":"uv","version":"0.9.28","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Debian GNU/Linux","version":"13","id":"trixie","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / iflow_mcp_overseer66_comfyui_mcp_server-0.1.0-py3-none-any.whl
| Download URL | iflow_mcp_overseer66_comfyui_mcp_server-0.1.0-py3-none-any.whl |
|---|---|
| Size | 11.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c63bb158079b090b55d2bd47b8bf70cc2b4d8d5d902d7b3ff7fac1f93263767f
|
|
BLAKE2b-256 checksum How to use checksums |
7013500843c17acc51c586a0f15ae5aed6884316c2cfc2d4bd3ab06d7739415b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.28 {"installer":{"name":"uv","version":"0.9.28","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Debian GNU/Linux","version":"13","id":"trixie","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for iflow-mcp_overseer66_comfyui-mcp-server 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.