| FMRS | 55 / 100 · C | 75 / 100 · B | 73 / 100 · B |
|---|
| Reliability | 9 / 20 | 13 / 20 | 12 / 20 |
|---|
| Security and permissions | 8 / 20 | 12 / 20 | 13 / 20 |
|---|
| Maintenance | 11 / 20 | 16 / 20 | 16 / 20 |
|---|
| Documentation | 14 / 20 | 17 / 20 | 16 / 20 |
|---|
| Setup experience | 13 / 20 | 17 / 20 | 16 / 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.
| - Scenarios needing clean, structured web context fed to an AI assistant
- Users already on the Firecrawl platform who want to call its scraping capability directly via MCP
| - Q&A and research scenarios that need real-time, clean web content
- Users with an existing Exa account who want a zero-deployment remote option
|
|---|
| 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.
| - Simple static-page scraping where you don't want to depend on a third-party API and incur call costs
- Sites that explicitly disallow automated access (robots.txt)
| - Scenarios requiring a strict allowlist of search sources that can't use a third-party search service
- Budget-sensitive, high-volume search scenarios (remote/API calls may incur cost)
|
|---|
| 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 a Firecrawl API key to call; cost and quota are governed by the Firecrawl account
- firecrawl_agent/firecrawl_interact perform automated browser interaction, which may trigger login or form-submission flows on the target site
| - Requires an Exa API key for full functionality; OAuth login is optional in remote mode
- web_fetch_exa retrieves content from a specified URL; agent_run performs multi-step autonomous actions and needs the user to have clear expectations of Agent behavior
|
|---|
| 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.
| - Bulk crawl/map tools can generate significant request volume against a target site — respect the site's rate limits and terms of service
- firecrawl_agent's interactive action chain is longer — define task boundaries clearly before running it to avoid accidentally triggering actions on a sensitive site
| - The API key should be stored carefully — avoid leaving it in plaintext in client config files on untrusted machines
- agent_run is a multi-step autonomous tool with a longer action chain — try it on low-risk tasks first
|
|---|
| Supported clients | Claude Desktop, Claude Code, MCP Inspector, Hermes, OpenClaw, Copilot CLI, Ollama | Claude Desktop, VS Code, Cursor, Windsurf, Zed, Amp | Claude Desktop, Claude Code, VS Code, Cursor, Windsurf, Zed, Amp, Kiro, LM Studio, Antigravity |
|---|
| Tools | 44 | 11 | 4 |
|---|