Homebutler vs Tickstem MCP
A side-by-side look at the Homebutler and Tickstem MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Homebutler for monitoring work as a local process; choose Tickstem MCP 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 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.
Choose Tickstem MCP when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
TICKSTEM_API_KEY, TICKSTEM_BASE_URL. - You want tools like
list_jobs, get_job, register_job.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 71/100 · Great | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | API key required |
| Pricing | Free | Not declared |
| Required env vars | None listed | TICKSTEM_API_KEYTICKSTEM_BASE_URL |
| Verified owner | Community listing | Community listing |
| GitHub stars | 305 | 2 |
| Directory activity | 4 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 40 | 26 |
| Full listing | View Homebutler | View Tickstem MCP |
Tools & capabilities
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
Tickstem MCP tools 26
list_jobsList all cron jobs in the accountget_jobGet a cron job by IDregister_jobRegister a new cron job (name, schedule, endpoint)update_jobUpdate an existing job — only provided fields changepause_jobPause a job so it no longer firesresume_jobResume a paused or failing jobdelete_jobPermanently delete a job and its execution historylist_executionsList execution history for a job, most recent firstlist_monitorsList all monitors — status, URL, interval, SSL expiry, assertionscreate_monitorCreate a monitor with optional response assertions (status code, response time, body)get_monitorGet a monitor by IDpause_monitorPause a monitor so it stops polling- +14 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.
Homebutler
{
"mcpServers": {
"higangssh-homebutler": {
"command": "npx",
"args": [
"-y",
"homebutler@latest"
]
}
}
}
Tickstem MCP
{
"mcpServers": {
"tickstem-mcp": {
"command": "uvx",
"args": [
"tickstem"
],
"env": {
"TICKSTEM_API_KEY": "YOUR_TICKSTEM_API_KEY_HERE",
"TICKSTEM_BASE_URL": "YOUR_TICKSTEM_BASE_URL_HERE"
}
}
}
}
Frequently asked questions
Homebutler is categorized under Monitoring and uses a local stdio subprocess. Tickstem MCP belongs to Monitoring and uses a local stdio subprocess. Pick Homebutler for monitoring work and Tickstem MCP 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.
Homebutler is listed as free. Auth: no auth required. Tickstem MCP has no declared pricing — check the project's own site. 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 higangssh-homebutler and tickstem-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Homebutler has a quality signal of 71/100 (Great) with 4 views, 0 installs and 305 GitHub stars. Tickstem MCP has 55/100 (Good) with 3 views, 0 installs and 2 GitHub stars.