RadioChron vs Homebutler
A side-by-side look at the RadioChron and Homebutler MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose RadioChron for monitoring work as a local process; choose Homebutler for monitoring as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose RadioChron when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
RADIOCHRON_CHRONICLE_PATH. - You want tools like
diagnose_incident, wifi_status, wifi_networks.
Choose Homebutler when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
proxmox_status, proxmox_guests, proxmox_node.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 53/100 · Good | 71/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | RADIOCHRON_CHRONICLE_PATH | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 305 |
| Directory activity | 2 views 0 installs 0 upvotes | 6 views 0 installs 0 upvotes |
| Tools | 17 | 40 |
| Full listing | View RadioChron | View Homebutler |
Tools & capabilities
RadioChron tools 17
diagnose_incidentOrchestrate Wi-Fi, connectivity, history, chronicle, and optional native BLE evidence in one compact responsewifi_statusCurrent state of every WLAN interfacewifi_networksNearby BSS records with real dBm, security, width, and load; summary or full detailwifi_analyzeSignal, contention, roaming, security, and scan-quality findingswifi_sampleCancelable RSSI/rate/roaming sampling with progresswifi_scanNative Wi-Fi refresh with per-interface completion/failureconnectivity_diagnoseSeparate radio, authentication, IP assignment, gateway, DNS, TCP, portal, TLS, quality, and Internet stageschronicle_startStart the local rotating change-only JSONL recorderchronicle_stopStop and flush the recorderchronicle_statusRecorder state, path, counters, and latest errorchronicle_recentRecent entries from active and rotated filesble_scanScan native adapters without connecting, normalize advertisements, update histories, and return risk evidence- +5 more on the listing page
Homebutler tools 40
proxmox_statusGet Proxmox VE version, cluster status, and resourcesproxmox_guestsList Proxmox QEMU and LXC guests, optionally filtered by node, status, or typeproxmox_nodeGet detailed Proxmox node statusproxmox_tasksGet the 50 most recent Proxmox tasks for a nodesystem_statusGet system status including CPU, memory, disk usage, and uptimeproxmox_guest_startStart one explicitly targeted Proxmox guest after confirmation and return the accepted task UPIDproxmox_guest_rebootReboot one explicitly targeted Proxmox guest after confirmation and return the accepted task UPIDproxmox_guest_shutdownGracefully shut down one explicitly targeted Proxmox guest after confirmation and return the accepted task UPIDproxmox_task_statusInspect one asynchronous Proxmox task by node and opaque UPIDproxmox_script_listList the curated Proxmox VE Community Scripts catalog (community-scripts/ProxmoxVE)proxmox_script_commandRender the pinned install command for one Proxmox VE Community Script. Never fetches or runs it; the caller reviews and runs it themselves on the Proxmox hostdocker_listList Docker containers with their status, image, and ports- +28 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.
RadioChron
{
"mcpServers": {
"radiochron": {
"command": "npx",
"args": [
"-y",
"radiochron-mcp"
],
"env": {
"RADIOCHRON_CHRONICLE_PATH": "YOUR_RADIOCHRON_CHRONICLE_PATH_HERE"
}
}
}
}
Homebutler
{
"mcpServers": {
"higangssh-homebutler": {
"command": "npx",
"args": [
"-y",
"homebutler@latest"
]
}
}
}
Frequently asked questions
RadioChron is categorized under Monitoring and uses a local stdio subprocess. Homebutler belongs to Monitoring and uses a local stdio subprocess. Pick RadioChron for monitoring work and Homebutler for monitoring.
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.
RadioChron has no declared pricing — check the project's own site. Homebutler is listed as free. Auth: no auth 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 radiochron and higangssh-homebutler as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, RadioChron has a quality signal of 53/100 (Good) with 2 views, 0 installs and 1 GitHub stars. Homebutler has 71/100 (Great) with 6 views, 0 installs and 305 GitHub stars.