Homebutler vs MCP Kafka

A side-by-side look at the Homebutler and MCP Kafka MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Homebutler logoHomebutlerMonitoring · Local subprocess (stdio)All-in-one homelab management MCP server. Monitor system resources, manage Docker containers, Wake-on-LAN, scan networks, check open ports, and run alerts — across multiple servers via SSH. Single 10MB binary, zero dependencies.71GreatAuth: no auth requiredMCP Kafka logoMCP KafkaMonitoring · Local subprocess (stdio)Apache Kafka monitoring & management for AI agents (with consumer lag) — governed.61GoodAuth: not declared

Verdict: choose Homebutler for monitoring work as a local process; choose MCP Kafka for monitoring as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Homebutler logoChoose 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.
Explore Homebutler

MCP Kafka logoChoose MCP Kafka when

  • You need dedicated capabilities in the Monitoring domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like cluster_info, list_topics, describe_topic.
Explore MCP Kafka

Feature & specification comparison

Rows where the two servers differ are marked.

SpecHomebutler logoHomebutlerMCP Kafka logoMCP Kafka
CategoryMonitoringMonitoring
Quality signal71/100 · Great61/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNo auth requiredNot declared
PricingFreeNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars3051
Directory activity 5 views 0 installs 0 upvotes 6 views 0 installs 0 upvotes
Tools406

Tools & capabilities

Homebutler tools 40

  • proxmox_statusGet Proxmox VE version, cluster status, and resources
  • proxmox_guestsList Proxmox QEMU and LXC guests, optionally filtered by node, status, or type
  • proxmox_nodeGet detailed Proxmox node status
  • proxmox_tasksGet the 50 most recent Proxmox tasks for a node
  • system_statusGet system status including CPU, memory, disk usage, and uptime
  • proxmox_guest_startStart one explicitly targeted Proxmox guest after confirmation and return the accepted task UPID
  • proxmox_guest_rebootReboot one explicitly targeted Proxmox guest after confirmation and return the accepted task UPID
  • proxmox_guest_shutdownGracefully shut down one explicitly targeted Proxmox guest after confirmation and return the accepted task UPID
  • proxmox_task_statusInspect one asynchronous Proxmox task by node and opaque UPID
  • proxmox_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 host
  • docker_listList Docker containers with their status, image, and ports
  • +28 more on the listing page

MCP Kafka tools 6

  • cluster_infoDescribe the Kafka cluster: brokers, controller, and cluster id.
  • list_topicsList topic names. Topics outside the allowlist are filtered out.
  • describe_topicPartitions, replicas, in-sync replicas, and non-default configs for a topic.
  • topic_offsetsEarliest and latest offsets per partition for a topic (message backlog view).
  • list_consumer_groupsList consumer groups and their protocol types.
  • describe_consumer_groupDescribe a consumer group's state and compute per-partition and total lag across its topics.

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 (Claude Desktop / Cursor)
{
  "mcpServers": {
    "higangssh-homebutler": {
      "command": "npx",
      "args": [
        "-y",
        "homebutler@latest"
      ]
    }
  }
}

MCP Kafka

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "mcp-kafka": {
      "command": "npx",
      "args": [
        "-y",
        "@dockndevai/mcp-kafka"
      ]
    }
  }
}

Frequently asked questions

Homebutler is categorized under Monitoring and uses a local stdio subprocess. MCP Kafka belongs to Monitoring and uses a local stdio subprocess. Pick Homebutler for monitoring work and MCP Kafka 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. MCP Kafka 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 higangssh-homebutler and mcp-kafka 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 5 views, 0 installs and 305 GitHub stars. MCP Kafka has 61/100 (Good) with 6 views, 0 installs and 1 GitHub stars.