MCP Server vs Homebutler

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

MCP Server logoMCP ServerMonitoring · Remote HTTP/SSEThinkNEO Control Plane — Enterprise AI governance MCP server with runtime guardrails, observability, AI FinOps, and agent lifecycle control.56GoodAuth: 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 MCP Server for monitoring work over a hosted endpoint; 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?

MCP Server logoChoose MCP Server when

  • You need dedicated capabilities in the Monitoring domain.
  • You prefer a remote HTTP/SSE transport.
  • Its auth model fits you: API key required.
  • You want tools like thinkneo_check_spend, thinkneo_complete, thinkneo_read_memory.
Explore MCP Server

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.

SpecMCP Server logoMCP ServerHomebutler logoHomebutler
CategoryMonitoringMonitoring
Quality signal56/100 · Good71/100 · Great
Install commandConfirmedConfirmed
TransportRemote HTTP/SSELocal subprocess (stdio)
AuthAPI key requiredNo auth required
PricingFreemiumFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars3304
Directory activity 2 views 0 installs 0 upvotes 4 views 0 installs 0 upvotes
Tools6840

Tools & capabilities

MCP Server tools 68

  • thinkneo_check_spendCheck AI spend summary for a workspace, team, or project. Returns real cost breakdown by provider, model, and time period from the ThinkNEO AI gateway.
  • thinkneo_completeRun a governed LLM completion through the ThinkNEO AI gateway. The request is authorized, classified, and policy-checked against your workspace governance BEFORE any provider is called — a blocked prompt never reaches the model. Tenant/workspace are derived from your API key.
  • thinkneo_read_memoryRead Claude Code project memory files. Without arguments, returns the MEMORY.md index listing all available memories. With a filename argument, returns the full content of that specific memory file. Use this to access project context, user preferences, feedback, and reference notes persisted across Claude Code sessions.
  • thinkneo_write_memoryWrite or update a Claude Code project memory file (.md). Persists project context, user preferences, feedback, and reference notes across Claude Code sessions. Filename must end in .md with lowercase alphanumeric characters. Path traversal is blocked. Requires authentication.Use this to persist project context, user preferences, feedback, and reference notes across Claude Code sessions. The filename must end in .md and contain only lowercase letters, digits, underscores, and hyphens (e.g. 'user_fabio.md', 'project_new_feature.md'). Path traversal is blocked.
  • thinkneo_evaluate_guardrailEvaluate a prompt or text against ThinkNEO guardrail policies before sending it to an AI provider. Returns risk assessment, violations found, and recommendations. Requires authentication.
  • thinkneo_checkFree-tier prompt safety check. Analyzes text for prompt injection patterns and PII (credit card numbers, Brazilian CPF, US SSN, email, phone, passwords). Returns a safety assessment with specific warnings. No authentication required.
  • thinkneo_check_policyCheck AI governance policies including model access, budget limits, data controls, and agent governance from the ThinkNEO gateway.
  • thinkneo_get_budget_statusCheck AI budget status including spend vs limit, forecast, and chargeback data from the ThinkNEO gateway.
  • thinkneo_list_alertsList active alerts for budget, policy, SLA, and security from the ThinkNEO gateway.
  • thinkneo_get_compliance_statusGet compliance status including framework coverage (EU AI Act, ISO 42001, NIST AI RMF, SOC 2) and governance assessments from the ThinkNEO gateway.
  • thinkneo_provider_statusGet real-time health and performance status of AI providers routed through the ThinkNEO gateway. Shows latency, error rates, and availability. No authentication required.
  • thinkneo_schedule_demoSchedule a demo or discovery call with the ThinkNEO team. Collects contact information and preferences. No authentication required.
  • +56 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.

MCP Server

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "thinkneoai-mcp-server": {
      "url": "https://mcp.thinkneo.ai/mcp"
    }
  }
}

Homebutler

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

Frequently asked questions

MCP Server is categorized under Monitoring and uses a remote HTTP/SSE transport. Homebutler belongs to Monitoring and uses a local stdio subprocess. Pick MCP Server 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.

MCP Server is listed as freemium — a free tier with paid plans. 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 thinkneoai-mcp-server and higangssh-homebutler as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, MCP Server has a quality signal of 56/100 (Good) with 2 views, 0 installs and 3 GitHub stars. Homebutler has 71/100 (Great) with 4 views, 0 installs and 304 GitHub stars.