| FMRS | 55 / 100 · C | 75 / 100 · B |
|---|
| Reliability | 9 / 20 | 10 / 20 |
|---|
| Security and permissions | 8 / 20 | 16 / 20 |
|---|
| Maintenance | 11 / 20 | 18 / 20 |
|---|
| Documentation | 14 / 20 | 17 / 20 |
|---|
| Setup experience | 13 / 20 | 14 / 20 |
|---|
| Best for | - Users who want an agent to operate ComfyUI rather than only relay prompts.
- Local GPU, LAN, VPS, RunPod, and Comfy Cloud users.
- Creators who need model-specific generation skills, workflow recipes, and troubleshooting.
- Users of Claude Code, Claude Desktop, or other MCP-capable agents.
| - Biomedical researchers
- Clinicians
- AI agents that need efficient access to biomedical literature and data analysis
|
|---|
| Not for | - Minimal connector use cases that only forward prompts and return images.
- Users without a ComfyUI instance or reachable remote ComfyUI.
- Models that do not support tool calling.
- Users seeking official Comfy maintenance or an official cloud-service guarantee.
| - 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 | - Requires access to the ComfyUI REST API and WebSocket.
- Local mode may read and write model, input, output, and workflow-library directories.
- Process-control features may start, stop, or restart local ComfyUI.
- Model and node discovery or downloads may access Hugging Face, CivitAI, GitHub, and the ComfyUI Registry; some features require tokens.
- Comfy Cloud mode requires COMFYUI_API_KEY.
| - 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 | - Workflow execution can consume local GPU VRAM, compute, and disk space.
- Downloaded models and custom nodes can be large and may include third-party code.
- stop_comfyui, restart_comfyui, and queue operations can interrupt jobs or unsaved workflow changes.
- Remote HTTP, tunnel, or bridge deployments increase network exposure and should use tokens and access controls.
- Hosted API nodes may consume paid API credits.
| - 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 Desktop, Claude Code, MCP Inspector, Hermes, OpenClaw, GitHub Copilot CLI, Ollama | Claude Desktop, Claude Code, Codex, Other MCP stdio clients |
|---|
| Tools | 44 | 11 |
|---|