OpenBio Comfy MCP
Click on "Install 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., "@OpenBio Comfy MCPAdd a group called 'upscaler' around the selected nodes"
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.
OpenBio Comfy MCP
OpenBio Comfy MCP is a local Model Context Protocol server and ComfyUI V3 extension for inspecting and editing the workflow currently open on a live ComfyUI canvas. It uses ComfyUI's native graph, selection, group, dirty-state, and undo behavior; it never queues, executes, or saves a workflow automatically.
Published releases are installable through ComfyUI Manager. Registry packages include a bundled MCP server, so Manager users do not need to runnpm ci.
Features
Inspect the active canvas as compact, structured MCP output.
Search all node types installed in the connected ComfyUI instance.
Inspect the complete native schema of an exact node type.
Select and focus native nodes or groups without modifying the workflow.
Add, remove, connect, disconnect, configure, and move nodes.
Add, update, fit, move, and remove native ComfyUI groups.
Apply a batch as one atomic, undoable native ComfyUI transaction.
Reject stale or invalid patches before changing the live graph.
Keep the MCP transport local: the stdio server opens no listening port, and canvas commands are accepted by the relay from loopback only.
Related MCP server: comfy-mcp
Architecture
MCP host application (Codex or another local host)
| MCP over stdio
v
Node.js MCP server
| ComfyUI HTTP
v
Python V3 extension relay
| ComfyUI WebSocket event
v
Browser page extension -> active app.canvas.graphThe browser page is the authority for the live graph. The Python extension correlates requests with a connected page, while the Node.js stdio server keeps no authoritative workflow copy. The extension registers no ComfyUI execution nodes and does not patch ComfyUI Core, ComfyUI_frontend, Desktop, or the workflow file format.
Requirements
ComfyUI 0.33.0 or newer
Python 3.10 or newer in the ComfyUI runtime
Node.js 20 or newer
An MCP host application that supports local stdio servers
A ComfyUI browser or Desktop page kept open while the tools are used
The ComfyUI extension has no additional Python package dependencies. Registry releases include a prebuilt MCP server. For source and development checkouts, npm ci installs only Node.js dependencies and builds that server; it does not modify the ComfyUI Python environment.
Install
ComfyUI Manager (recommended)
Open ComfyUI Manager, search for OpenBio Comfy MCP or openbio-comfy-mcp, select Install, and restart ComfyUI. The installed MCP entry point is:
<ComfyUI>/custom_nodes/openbio-comfy-mcp/dist/openbio-comfy-mcp.mjsNo npm ci step is required for a Registry installation.
Standard source installation
Clone the repository directly into ComfyUI's custom_nodes directory, then install the MCP server dependency and build the bundled entry point.
Windows PowerShell:
$ComfyRoot = "C:\path\to\ComfyUI"
Set-Location "$ComfyRoot\custom_nodes"
git clone https://github.com/Open-Bio/openbio-comfy-mcp.git
Set-Location .\openbio-comfy-mcp
npm ciLinux or macOS:
cd /path/to/ComfyUI/custom_nodes
git clone https://github.com/Open-Bio/openbio-comfy-mcp.git
cd openbio-comfy-mcp
npm ciRestart ComfyUI after installation, open its UI in a browser, and verify that the extension route is available:
Invoke-RestMethod http://127.0.0.1:8188/openbio-comfy-mcp/healthThe expected response is { "ok": true }.
Sibling checkout for development
Keep the Git checkout outside ComfyUI and expose it through a link when you want edits to remain in a standalone repository.
Windows PowerShell:
$ComfyRoot = "C:\path\to\ComfyUI"
$Repo = "C:\path\to\openbio-comfy-mcp"
New-Item -ItemType Junction `
-Path "$ComfyRoot\custom_nodes\openbio-comfy-mcp" `
-Target $Repo
Set-Location $Repo
npm ciLinux or macOS:
ln -s /path/to/openbio-comfy-mcp /path/to/ComfyUI/custom_nodes/openbio-comfy-mcp
cd /path/to/openbio-comfy-mcp
npm ciDo not expose the same checkout through more than one custom-node root.
Connect an MCP host
Codex
Register the local stdio server with an absolute path:
$Repo = (Resolve-Path "C:\path\to\openbio-comfy-mcp").Path
codex mcp add openbio-comfy-mcp `
--env OPENBIO_COMFY_URL=http://127.0.0.1:8188 `
-- node "$Repo\dist\openbio-comfy-mcp.mjs"
codex mcp get openbio-comfy-mcp --json
codex mcp list --jsonRestart the Codex client after adding the server. Codex Desktop, the CLI, and the IDE extension share MCP configuration on the same Codex host. See the official Codex MCP documentation.
Other stdio MCP hosts
For hosts that use an mcpServers JSON configuration, adapt this example with an absolute path:
{
"mcpServers": {
"openbio-comfy-mcp": {
"command": "node",
"args": ["C:\\path\\to\\openbio-comfy-mcp\\dist\\openbio-comfy-mcp.mjs"],
"env": {
"OPENBIO_COMFY_URL": "http://127.0.0.1:8188"
}
}
}
}Configuration keys vary by host. The command must start dist/openbio-comfy-mcp.mjs, and OPENBIO_COMFY_URL must point to the local ComfyUI server.
Configuration
Variable | Default | Description |
|
| Base URL of the ComfyUI server used by the local MCP server. |
Tools
Tool | Effect | Purpose |
| Read-only | Inspect compact topology or details for exact native node/group refs. |
| Read-only | Search the connected ComfyUI |
| Read-only | Read the complete native schema for one exact |
| UI state only | Select and optionally fit native items without modifying the workflow. |
| Writes the live canvas | Apply one atomic, undoable batch of typed node, link, or group operations. |
Recommended editing flow:
Call
inspect_canvasand keep the returnedcanvas_idandrevision.Use
search_nodesandinspect_node_typebefore adding an unfamiliar node type.Send one
apply_canvas_patchwith the inspectedcanvas_idandrevisionasbase_revision.Optionally call
present_canvasto select and focus the changed items.Inspect again. If the result is unwanted, use ComfyUI's native undo command.
See docs/spec.md for the exact public behavior and operation set.
Frontend development note
The standalone ComfyUI_frontend Vite development server (pnpm dev, normally port 5173) does not load JavaScript extensions supplied by custom nodes. OpenBio Comfy MCP therefore cannot connect to a canvas served only by that development server. Use the frontend served by ComfyUI itself, or build the frontend and launch ComfyUI with that build as its frontend root.
After installing or updating this repository, restart ComfyUI and reload the browser page so the page extension is loaded.
Security and privacy
Install MCP servers only from sources you trust. This local server runs with the same operating-system permissions as the MCP host application that launches it.
Treat
apply_canvas_patchas a write-capable tool and review or approve its use in your MCP host. It changes the workflow currently open in the selected page, although the whole patch can be reverted with one native undo.The stdio MCP server opens no network listener. It calls the configured ComfyUI HTTP server, which defaults to
http://127.0.0.1:8188.Canvas command requests are accepted from loopback only. This restriction is not a general authentication layer for ComfyUI; do not expose an unauthenticated ComfyUI server to untrusted networks.
The bridge exposes typed graph operations, not arbitrary JavaScript, DOM access, filesystem access, shell commands, workflow queueing, or execution.
Canvas inspections can include workflow names, paths, node titles, prompts, filenames, sample identifiers, and widget values. Any onward handling follows the privacy policy and configuration of the MCP host and model provider you connect.
A disconnected page returns
NO_LIVE_CANVAS; the system never falls back to editing workflow files in the background.
Troubleshooting
NO_LIVE_CANVAS: open or reload a ComfyUI page and leave it connected.Tools are missing in the host: verify the absolute
dist/openbio-comfy-mcp.mjspath and restart the MCP host application. For a source checkout, runnpm cifirst.Health endpoint is missing: verify the repository is directly under
custom_nodesor linked there, then restart ComfyUI and inspect its console for import errors.STALE_CANVAS: callinspect_canvasagain and build a new patch from the returned revision.Multiple pages are open: the most recently focused ComfyUI page is the default target; an unresolved ambiguity is reported instead of guessed.
Port
5173development page does not connect: use a frontend served by the ComfyUI backend as described above.
Update and uninstall
Update a source installation and its locked Node.js dependencies:
git pull --ff-only
npm ciRestart ComfyUI and reload its browser page after an update.
To uninstall, first remove the MCP host registration. For Codex:
codex mcp remove openbio-comfy-mcpThen remove the cloned openbio-comfy-mcp directory—or only the Junction/symbolic link for a sibling development checkout—from ComfyUI/custom_nodes, and restart ComfyUI.
Development
Install Node.js dependencies and run the MCP/page-extension tests:
npm ci
npm testRun the Python relay tests with the same interpreter used by ComfyUI:
C:\path\to\ComfyUI\.venv\Scripts\python.exe `
-m pytest --rootdir=tests -c pyproject.toml tests -qRepository layout:
dist/ Bundled, dependency-free Registry MCP entry point
mcp_host/ Node.js stdio MCP server
openbio_comfy_mcp/ ComfyUI V3 Python relay extension
scripts/ Reproducible MCP bundle build
web/ Live page extension and canvas bridge
tests/ Node.js and Python tests
docs/spec.md Public behavior and safety boundariesIssues and pull requests are welcome. Please keep changes inside the project's documented live-canvas and local-transport boundaries, and run both test suites before submitting.
License
OpenBio Comfy MCP is released under the MIT License.
This project uses the official Model Context Protocol TypeScript SDK and ComfyUI's documented V3 extension and JavaScript extension mechanisms.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
Create, browse, remix, collaborate on, and run durable AI workflow nodes from MCP hosts.
Remote MCP server for RunComfy Serverless API (ComfyUI): deployments and async inference.
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
A Model Context Protocol server for Wix AI tools
Related MCP Servers
- AlicenseAqualityAmaintenanceThe MCP server that drafts ComfyUI workflows a human can actually read. It lets coding agents build, repair, port, validate, and run ComfyUI workflows against your own ComfyUI instance, delivering clean, organized, fully-labeled workflows.292MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that enables AI agents to control a local ComfyUI instance for image generation, allowing workflow understanding, parameter modification, execution, and model discovery.233Apache 2.0
- AlicenseAqualityCmaintenanceA universal MCP server that lets agents discover ComfyUI nodes, build/edit/run API workflows, manage queues, retrieve outputs, and optionally render graphs on a ComfyUI canvas.23Apache 2.0
- FlicenseNot gradedqualityCmaintenanceWindows-native MCP server for a local ComfyUI portable package. It enables listing, validating, and running ComfyUI workflows via the loopback HTTP API.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Open-Bio/openbio-comfy-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server