Rtcf vs MCP Arr
A side-by-side look at the Rtcf and MCP Arr 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 MCP Arr 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 MCP Arr when
- You need dedicated capabilities in the Multimedia Process domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You want tools like
arr_status, search, fetch.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Multimedia Process | Multimedia Process |
| Quality signal | 52/100 · Good | 69/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 234 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 3 | 11 |
| Full listing | View Rtcf | View MCP Arr |
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.
MCP Arr tools 11
arr_statusGet status of all supported *arr services. No local *arr services are currently configured, but TRaSH reference tools remain available.searchSearch across configured *arr libraries plus TRaSH Guides reference profiles. This is the primary discovery tool for remote MCP clients such as ChatGPT.fetchFetch a specific item returned by search. Accepts an opaque item id from the search tool.arr_search_allSearch across all configured *arr services for any mediatrash_list_profilesList available TRaSH Guides quality profiles for Radarr or Sonarr. Shows recommended profiles for different use cases (1080p, 4K, Remux, etc.)trash_get_profileGet a specific TRaSH Guides quality profile with all custom format scores, quality settings, and implementation detailstrash_list_custom_formatsList available TRaSH Guides custom formats. Can filter by category: hdr, audio, resolution, source, streaming, anime, unwanted, release, languagetrash_get_namingGet TRaSH Guides recommended naming conventions for your media server (Plex, Emby, Jellyfin, or standard)trash_get_quality_sizesGet TRaSH Guides recommended min/max/preferred sizes for each quality leveltrash_compare_profileCompare your quality profile against TRaSH Guides recommendations. Shows missing custom formats, scoring differences, and quality settings. Requires the corresponding *arr service to be configured.trash_compare_namingCompare your naming configuration against TRaSH Guides recommendations. Requires the corresponding *arr service to be configured.
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"
}
}
}
MCP Arr
{
"mcpServers": {
"mcp-arr": {
"command": "npx",
"args": [
"-y",
"mcp-arr-server"
]
}
}
}
Frequently asked questions
Rtcf is categorized under Multimedia Process and uses a remote HTTP/SSE transport. MCP Arr belongs to Multimedia Process and uses a local stdio subprocess. Pick Rtcf for multimedia process work and MCP Arr 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. MCP Arr is listed as free. Auth: api key required. 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 mcp-arr 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. MCP Arr has 69/100 (Great) with 3 views, 0 installs and 234 GitHub stars.