| FMRS | 69 / 100 · C | 75 / 100 · B |
|---|
| Reliability | 10 / 20 | 10 / 20 |
|---|
| Security and permissions | 15 / 20 | 16 / 20 |
|---|
| Maintenance | 13 / 20 | 18 / 20 |
|---|
| Documentation | 17 / 20 | 17 / 20 |
|---|
| Setup experience | 14 / 20 | 14 / 20 |
|---|
| Best for | - Users whose machine can carry local diffusion (a discrete GPU with >= 24 GB VRAM is ideal; Apple Silicon with >= 32 GB unified memory is OK for images)
- Users who want to automate a local ComfyUI workflow from Claude Code, Claude Desktop, Cursor or any MCP-speaking client
- Users who need to introspect live nodes, models and templates, custom nodes included
- Users running a local LLM and ComfyUI on the same GPU who need the read/free VRAM loop
| - Biomedical researchers
- Clinicians
- AI agents that need efficient access to biomedical literature and data analysis
|
|---|
| Not for | - Users who want Comfy Cloud execution, cloud queue or cross-session cloud batches — this server has no path to Comfy Cloud, use https://cloud.comfy.org/mcp instead
- Machines with under 8 GB VRAM or a confirmed absence of a GPU (use partner nodes or the cloud MCP)
- Users who need lifecycle management (launch/stop/update/version-switch/install nodes/logs) on a remote box — those tools are local-only
- Users running the MCP on a remote or containerised host who need the browser sign-in callback to land on their machine
| - Users needing to write to upstream databases (read-only)
- Users requiring direct access to closed datasets (e.g., COSMIC is not directly integrated)
- Users expecting all advanced features without API keys
|
|---|
| Required permissions | - Runs the comfy command as a subprocess on your machine, carrying the server process's full environment
- Reads ComfyUI workspace files, including workflow JSON and input assets
- Writes generated outputs, by default into the ComfyUI workspace's output/ directory; fetch_outputs can copy them to a directory you name
- Writes/installs models and node packs on this machine (download_model, install_node)
- Reads, launches, stops or restarts the local ComfyUI process
- launch_comfyui with --listen exposes an unauthenticated ComfyUI to the network and requires explicit confirmation
- COMFY_API_KEY is used for partner-API nodes and can spend Comfy credits through those nodes
- COMFY_MCP_ASSUME_CONSENT can pre-authorize the install_node, update_all, version_switch, kill_untracked and network_exposure gates (spending is excluded)
| - Requires internet access to query public biomedical APIs
- Optional API keys (NCBI, Semantic Scholar, OpenFDA, etc.) to improve rate limits or unlock features
- Local read/write access for skills, cache, and local study data (e.g., `~/.local/share/biomcp`)
|
|---|
| Risks and side effects | - Partner generation (partner_generate, workflows or templates containing partner-API nodes) really spends Comfy credits and is confirmed at call time; an agent host's 'always allow this tool' toggle is never treated as spend consent
- An arbitrary custom node can still call a paid service of its own — the confirm_spend gate only covers partner-API nodes comfy-cli recognizes, so check a workflow you did not build before running it
- launch_comfyui with --listen binds an unauthenticated ComfyUI to your network, exposing it to others
- Installing node packs, switching versions, updating ComfyUI and force-restarting a server it did not start modify your local environment; tools fail closed when the client does not show the confirmation prompt
- With a remote COMFYUI_URL configured, system_stats / free_memory still act on the local install, so you may measure and free the wrong machine; the remote ComfyUI must be reachable and unauthenticated on that network
- COMFY_MCP_ASSUME_CONSENT is a setting written in your client config; granting too much silently widens the risks above
- The server is beta, so behaviour may change
| - Upstream API rate limits may affect performance
- Some data sources (e.g., KEGG) have licensing terms that restrict non-academic use
- Features requiring API keys (e.g., OncoKB) may be incomplete without them
- Local binary installations need regular updates for compatibility
|
|---|
| Supported clients | Claude Code, Claude Desktop, Cursor | Claude Desktop, Claude Code, Codex, Other MCP stdio clients |
|---|
| Tools | 30 | 11 |
|---|