Rtcf vs Comfyui MCP
A side-by-side look at the Rtcf and Comfyui MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Rtcf for multimedia process work over a hosted endpoint; choose Comfyui MCP for multimedia process as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Rtcf when
- You need dedicated capabilities in the Multimedia Process domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
improve_prompt, improve_followup, build_prompt.
Choose Comfyui MCP when
- You need dedicated capabilities in the Multimedia Process domain.
- You prefer a local stdio subprocess transport.
- You want tools like
queue, get_system_stats, visualize_workflow.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Multimedia Process | Multimedia Process |
| Quality signal | 52/100 · Good | 64/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 861 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 3 | 13 |
| Full listing | View Rtcf | View Comfyui MCP |
Tools & capabilities
Rtcf tools 3
improve_promptRewrite a rough prompt into a sharper, ready-to-use prompt structured as Role, Task, Context, Format (RTCF). Returns the improved prompt, its four parts, a short list of clarifying questions worth asking the user, and which model tier and effort level suit this kind of work. Use this before answering when the user's request is vague, or when the user asks to improve a prompt.improve_followupWrite the user's NEXT message for an AI conversation that is already in progress (a follow-up). Use when the user wants to refine, deepen, or continue earlier work in this conversation. Do NOT use it for a brand-new task (use improve_prompt for that). Returns a short, ready-to-send continuation message that anchors to the existing work instead of restarting it. Requires an API key (add ?key=rk_live_... to the connector URL).build_promptCompose a ready-to-use prompt from explicit Role, Task, Context, and Format parts. Use when the user already knows the pieces and wants them woven into one clean prompt.
Comfyui MCP tools 13
queueOne action-parameterized tool for the execution queue: `list` (running + pending), `status` (one job by prompt ID), `get_workflow` (a pending job's full payload), `move`/`edit` (requeue a pending job front/back, patched or replaced, with a new prompt ID), `cancel` (interrupt the running job — escal…get_system_statsGet system info — GPU, VRAM, Python version, OSvisualize_workflowOne action-parameterized tool for rendering and converting a workflow you pass in: `render` (Mermaid flowchart, nodes grouped by category), `render_hierarchical` (the same graph sectioned — overview, one section in detail, a listing, or an AI-oriented summary), `mermaid` (a Mermaid diagram back to…create_workflowOne action-parameterized tool for authoring: `create` (from templates: `txt2img`, `img2img`, `upscale`, `inpaint`, `controlnet`, `ip_adapter`, `ace_step_15`, `stable_audio_3`), `modify` (operations: `set_input`, `add_node`, `remove_node`, `connect`, `insert_between`), `validate` (dry-run — missing…get_workflowOne action-parameterized tool for READING a saved workflow file: `list` (the user library, subfolders included), `get` (one workflow's JSON by filename), `analyze` (a structured summary instead of raw JSON), `query` (filter/traverse/aggregate a big graph without dumping it), `strip` (**de-virtualiz…save_workflowOne action-parameterized tool for WRITING to the library: `save` (store a workflow — overwrites a same-filename file), `lock` (record a provenance lock: SHA-256 per model, git commit per node pack), `verify_lock` (report drift against that lock)upload_imageCopy a local image into ComfyUI's `input/` directory for img2img, inpaint, or ControlNetdownload_modelFind and fetch model weights, and track the transfers. `action`: `download` (from a URL, into the correct ComfyUI subdirectory), `status`, `cancel`, `search` (HuggingFace), `search_civitai`, `search_creators`, `download_civitai`, `resolve_missinglist_local_modelsWhat is installed, and where ComfyUI looks. `action`: `list` (installed models by type: checkpoints, loras, vae, upscale_models, controlnet, embeddings, clip, unet, diffusion_models, text_encoders), `remove` (**deletes a model file**), `embeddings`, `list_paths`, `add_path`, `remove_path` (the last…clear_vramFree GPU VRAM by unloading cached models — calls ComfyUI's `/free` endpoint, reports before/after statssearch_custom_nodesSearch the ComfyUI Registry for node packs by keyword (`action: "search"`), or get one pack's full details (`action: "details"`)comfy_cliSearch actual loaded node classes through official `comfy nodes search` (action:"search_nodes")- +1 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Rtcf
{
"mcpServers": {
"rtcf": {
"url": "https://rtcf.happlen.com/api/mcp"
}
}
}
Comfyui MCP
{
"mcpServers": {
"comfyui-mcp-2": {
"command": "npx",
"args": [
"-y",
"comfyui-mcp@latest"
]
}
}
}
Frequently asked questions
Rtcf is categorized under Multimedia Process and uses a remote HTTP/SSE transport. Comfyui MCP belongs to Multimedia Process and uses a local stdio subprocess. Pick Rtcf for multimedia process work and Comfyui MCP for multimedia process.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Rtcf has no declared pricing — check the project's own site. Comfyui MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add rtcf and comfyui-mcp-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Rtcf has a quality signal of 52/100 (Good) with 0 views, 0 installs and 0 GitHub stars. Comfyui MCP has 64/100 (Good) with 2 views, 0 installs and 861 GitHub stars.