What is the key difference between Fritzbox MCP Server and Plugwise MCP?

Fritzbox MCP Server belongs to the Home Automation category with local stdio execution, while Plugwise MCP belongs to the Home Automation category with local stdio execution.

How do I install Fritzbox MCP Server or Plugwise MCP in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Fritzbox MCP Server and Plugwise MCP free or paid?

Fritzbox MCP Server operates under a Free / Open Source model (other). Plugwise MCP operates under a Free / Open Source model (other).

Which MCP server has more tools and community activity?

Fritzbox MCP Server lists 6 tools with 3 views and 18 GitHub stars. Plugwise MCP lists 16 tools with 2 views and 2 GitHub stars.

Can I use both Fritzbox MCP Server and Plugwise MCP together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Fritzbox MCP Server vs Plugwise MCP

In-depth architectural comparison of the Fritzbox MCP Server and Plugwise MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

Fritzbox MCP Server

Home Automation · Local stdio

Quality: 41/100 (Fair) | Auth: other

Plugwise MCP

Home Automation · Local stdio

Quality: 55/100 (Good) | Auth: other

Verdict Summary: Choose Fritzbox MCP Server if you need specialized Home Automation tools running via a local process. Choose Plugwise MCP if your workspace requires Home Automation integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Fritzbox MCP Server when:

You need dedicated capabilities in the Home Automation domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: other (Free / Open Source).
Primary tools included: Local FRITZ!Box communication, Device inventory and bandwidth inspection, WiFi and guest network management.

Explore Fritzbox MCP Server Details

Choose Plugwise MCP when:

You need dedicated capabilities in the Home Automation domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: other (Free / Open Source).
You have access to required keys: HUB1, HUB1IP, HUB2, HUB2IP, PLUGWISE_HOST, PLUGWISE_PASSWORD, OPENAI_API_KEY, PLUGWISE_AGENT_MODEL.
Primary tools included: .

Feature & Specification Comparison

Specification	Fritzbox MCP Server kambriso Home Automation	Plugwise MCP Tommertom Home Automation
Summary	Control AVM FRITZ!Box routers - manage devices, WiFi, network settings, parental controls, and schedule time-delayed actions	TypeScript-based smart home automation server for Plugwise devices with automatic network discovery. Features comprehensive device control for thermostats, switches, smart plugs, energy monitoring, multi-hub management, and real-time climate/power consumption tracking via local network integration.
Category & Scope

Tools & Capabilities Breakdown

Fritzbox MCP Server Tools (6)

Local FRITZ!Box communication

Device inventory and bandwidth inspection

WiFi and guest network management

Parental controls

Scheduled delayed actions

Network health and log analysis

Plugwise MCP Tools (16)

add_hub

Add a new Plugwise hub by providing its name (used as password). Scans the network to find the hub and stores it in the /hubs folder as a JSON file for future use. The hub name is the unique identifier printed on the back of your Plugwise device.

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Fritzbox MCP Server Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "kambriso-fritzbox-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "kambriso-fritzbox-mcp-server"
      ]
    }
  }
}

Plugwise MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "tommertom-plugwise-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "plugwise-mcp-server"
      ],
      "env": {
        "HUB1": "YOUR_HUB1_HERE",
        "HUB1IP": "YOUR_HUB1IP_HERE",
        "HUB2": "YOUR_HUB2_HERE",
        "HUB2IP": "YOUR_HUB2IP_HERE",
        "PLUGWISE_HOST": "YOUR_PLUGWISE_HOST_HERE",
        "PLUGWISE_PASSWORD": "YOUR_PLUGWISE_PASSWORD_HERE",
        "OPENAI_API_KEY": "YOUR_OPENAI_API_KEY_HERE",
        "PLUGWISE_AGENT_MODEL": "YOUR_PLUGWISE_AGENT_MODEL_HERE"
      }
    }
  }
}

Frequently Asked Questions

Fritzbox MCP Server is categorized under Home Automation and uses a local stdio subprocess. In contrast, Plugwise MCP belongs to Home Automation using local stdio subprocess. Select Fritzbox MCP Server when you need capabilities focused on home automation and Plugwise MCP when you require tools for home automation.

More alternatives to Fritzbox MCP Server More alternatives to Plugwise MCP Home Automation category hub