What is the key difference between Thinqconnect MCP and Plugwise MCP?

Thinqconnect MCP belongs to the Other Tools and Integrations category with local stdio execution, while Plugwise MCP belongs to the Other Tools and Integrations category with local stdio execution.

How do I install Thinqconnect 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 Thinqconnect MCP and Plugwise MCP free or paid?

Thinqconnect MCP operates under a Free / Open Source model (API Key required). Plugwise MCP operates under a Free / Open Source model (other).

Which MCP server has more tools and community activity?

Thinqconnect MCP lists 5 tools with 1 views and 30 GitHub stars. Plugwise MCP lists 6 tools with 2 views and 2 GitHub stars.

Can I use both Thinqconnect 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

Thinqconnect MCP vs Plugwise MCP

In-depth architectural comparison of the Thinqconnect 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

Thinqconnect MCP

Other Tools and Integrations · Local stdio

Quality: 39/100 (Fair) | Auth: API Key required

Plugwise MCP

Other Tools and Integrations · Local stdio

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

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

Which MCP Server Should You Choose?

Choose Thinqconnect MCP when:

You need dedicated capabilities in the Other Tools and Integrations domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: THINQ_PAT, THINQ_COUNTRY.
Primary tools included: Retrieve all registered ThinQ devices, Monitor device status, Query device control capabilities.

Explore Thinqconnect MCP Details

Choose Plugwise MCP when:

You need dedicated capabilities in the Other Tools and Integrations 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.

Feature & Specification Comparison

Specification	Thinqconnect MCP thinq-connect Other Tools and Integrations	Plugwise MCP Tommertom Other Tools and Integrations
Summary	Interact with LG ThinQ smart home devices and appliances through the ThinQ Connect MCP server.	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

Thinqconnect MCP Tools (5)

Retrieve all registered ThinQ devices

Monitor device status

Query device control capabilities

Send device control commands

Run through an stdio MCP connection

Plugwise MCP Tools (6)

Automatic Plugwise hub discovery

Thermostat, switch, and smart plug control

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

Thinqconnect MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "thinq-connect-thinqconnect-mcp": {
      "command": "uvx",
      "args": [
        "thinqconnect-mcp"
      ],
      "env": {
        "THINQ_PAT": "YOUR_THINQ_PAT_HERE",
        "THINQ_COUNTRY": "YOUR_THINQ_COUNTRY_HERE"
      }
    }
  }
}

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

Thinqconnect MCP is categorized under Other Tools and Integrations and uses a local stdio subprocess. In contrast, Plugwise MCP belongs to Other Tools and Integrations using local stdio subprocess. Select Thinqconnect MCP when you need capabilities focused on other tools and integrations and Plugwise MCP when you require tools for other tools and integrations.

More alternatives to Thinqconnect MCP More alternatives to Plugwise MCP Other Tools and Integrations category hub