Rtcf vs Imgx
A side-by-side look at the Rtcf and Imgx 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 Imgx 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 Imgx when
- You need dedicated capabilities in the Multimedia Process domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
GEMINI_API_KEY. - You want tools like
generate_image, edit_image, edit_last.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Multimedia Process | Multimedia Process |
| Quality signal | 52/100 · Good | 52/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 | GEMINI_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 1 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 3 | 10 |
| Full listing | View Rtcf | View Imgx |
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.
Imgx tools 10
generate_imageGenerate an image from a text promptedit_imageEdit an existing image with text instructionsedit_lastEdit the last generated/edited image (no input path needed)undo_editUndo the last edit, reverting to the previous image in the sessionredo_editRedo a previously undone editedit_historyShow all sessions and their edit history with metadataswitch_sessionSwitch to a different editing sessionclear_historyClear project history (optionally delete image files)set_output_dirChange the default output directory (optionally move existing files)list_providersList available providers and capabilities
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"
}
}
}
Imgx
{
"mcpServers": {
"imgx": {
"command": "npx",
"args": [
"-y",
"has"
],
"env": {
"GEMINI_API_KEY": "YOUR_GEMINI_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Rtcf is categorized under Multimedia Process and uses a remote HTTP/SSE transport. Imgx belongs to Multimedia Process and uses a local stdio subprocess. Pick Rtcf for multimedia process work and Imgx 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. Imgx 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 imgx 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. Imgx has 52/100 (Good) with 0 views, 0 installs and 1 GitHub stars.