What is the key difference between Sonos Ts MCP and Plugwise MCP?

Sonos Ts MCP 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 Sonos Ts MCP 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 Sonos Ts MCP and Plugwise MCP free or paid?

Sonos Ts MCP operates under a Free / Open Source model (No auth required). Plugwise MCP operates under a Free / Open Source model (other).

Which MCP server has more tools and community activity?

Sonos Ts MCP lists 60 tools with 3 views and 15 GitHub stars. Plugwise MCP lists 16 tools with 2 views and 2 GitHub stars.

Can I use both Sonos Ts MCP 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

Sonos Ts MCP vs Plugwise MCP

In-depth architectural comparison of the Sonos Ts MCP 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

Sonos Ts MCP

Home Automation · Local stdio

Quality: 56/100 (Good) | Auth: No auth required

Plugwise MCP

Home Automation · Local stdio

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

Verdict Summary: Choose Sonos Ts MCP 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 Sonos Ts MCP when:

You need dedicated capabilities in the Home Automation domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: sonos_agent, sonos_discover, sonos_add_device.

Explore Sonos Ts MCP 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: add_hub, list_hubs, connect.

Feature & Specification Comparison

Specification	Sonos Ts MCP Tommertom Home Automation	Plugwise MCP Tommertom Home Automation
Summary	Comprehensive Sonos audio system control through pure TypeScript implementation. Features complete device discovery, multi-room playback management, queue control, music library browsing, alarm management, real-time event subscriptions, and audio EQ settings. Includes 50+ tools for seamless smart home audio automation via UPnP/SOAP protocols.	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

Sonos Ts MCP Tools (60)

sonos_agent

AI-powered natural language control. Give instructions like "Play jazz in the living room" and the agent autonomously handles device discovery, tool selection, and execution. Only available when `OPENAI_API_KEY` or `GOOGLE_GENERATIVE_AI_API_KEY` is configured. See [Agent Tool Documentation](./docs/…

sonos_discover

Discover Sonos devices on the network using SSDP multicast

sonos_add_device

Manually add a Sonos device by IP address (useful when SSDP discovery fails)

sonos_list_devices

List all discovered/registered devices

sonos_play

Start playback

sonos_pause

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).

Sonos Ts MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "tommertom-sonos-ts-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "sonos-agent-cli"
      ]
    }
  }
}

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

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

More alternatives to Sonos Ts MCP More alternatives to Plugwise MCP Home Automation category hub Canonical compare URL