Langfuse MCP vs Homebutler

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

Langfuse MCP logoLangfuse MCPMonitoring · Local subprocess (stdio)Query Langfuse traces, debug exceptions, analyze sessions, and manage prompts. Full observability toolkit for LLM applications.65GreatAuth: api key requiredHomebutler 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 required

Verdict: choose Langfuse MCP 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?

Langfuse MCP logoChoose Langfuse 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: LANGFUSE_PUBLIC_KEY, LANGFUSE_SECRET_KEY, LANGFUSE_HOST, LANGFUSE_MCP_READ_ONLY.
  • You want tools like list_annotation_queues, create_annotation_queue, get_annotation_queue.
Explore Langfuse MCP

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

Feature & specification comparison

Rows where the two servers differ are marked.

SpecLangfuse MCP logoLangfuse MCPHomebutler logoHomebutler
CategoryMonitoringMonitoring
Quality signal65/100 · Great71/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthAPI key requiredNo auth required
PricingFreeFree
Required env varsLANGFUSE_PUBLIC_KEYLANGFUSE_SECRET_KEYLANGFUSE_HOSTLANGFUSE_MCP_READ_ONLYNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars113304
Directory activity 6 views 0 installs 0 upvotes 4 views 0 installs 0 upvotes
Tools4840

Tools & capabilities

Langfuse MCP tools 48

  • list_annotation_queuesList annotation queues with pagination.
  • create_annotation_queueCreate an annotation queue.
  • get_annotation_queueGet a single annotation queue by ID.
  • list_annotation_queue_itemsList items in an annotation queue.
  • get_annotation_queue_itemGet a specific annotation queue item by queue and item ID.
  • create_annotation_queue_itemCreate an annotation queue item.
  • update_annotation_queue_itemUpdate the status of an annotation queue item.
  • delete_annotation_queue_itemDelete an annotation queue item.
  • create_annotation_queue_assignmentAssign a user to an annotation queue.
  • delete_annotation_queue_assignmentUnassign a user from an annotation queue.
  • list_datasetsList all datasets in the project with pagination. Returns metadata about datasets including name, description, item count, and timestamps. Args: ctx: Context object containing lifespan context with Langfuse client page: Page number for pagination (starts at 1) limit: Maximum items per page (max 100) Returns: A dictionary containing: - data: List of dataset metadata objects - metadata: Pagination info (page, limit, total)
  • get_datasetGet a specific dataset by name. Retrieves dataset details including metadata and item count. Args: ctx: Context object containing lifespan context with Langfuse client name: The name of the dataset to fetch Returns: A dictionary containing dataset details: - id: Unique dataset identifier - name: Dataset name - description: Dataset description - metadata: Custom metadata - items: List of dataset items (if included by the API) - runs: List of dataset runs (if included by the API)
  • +36 more on the listing page

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

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.

Langfuse MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "avivsinai-langfuse-mcp": {
      "command": "uvx",
      "args": [
        "langfuse-mcp"
      ],
      "env": {
        "LANGFUSE_PUBLIC_KEY": "YOUR_LANGFUSE_PUBLIC_KEY_HERE",
        "LANGFUSE_SECRET_KEY": "YOUR_LANGFUSE_SECRET_KEY_HERE",
        "LANGFUSE_HOST": "YOUR_LANGFUSE_HOST_HERE",
        "LANGFUSE_MCP_READ_ONLY": "YOUR_LANGFUSE_MCP_READ_ONLY_HERE"
      }
    }
  }
}

Homebutler

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "higangssh-homebutler": {
      "command": "npx",
      "args": [
        "-y",
        "homebutler@latest"
      ]
    }
  }
}

Frequently asked questions

Langfuse MCP is categorized under Monitoring and uses a local stdio subprocess. Homebutler belongs to Monitoring and uses a local stdio subprocess. Pick Langfuse MCP 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.

Langfuse MCP is listed as free. Auth: api key required. 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 avivsinai-langfuse-mcp and higangssh-homebutler as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Langfuse MCP has a quality signal of 65/100 (Great) with 6 views, 0 installs and 113 GitHub stars. Homebutler has 71/100 (Great) with 4 views, 0 installs and 304 GitHub stars.