What is the key difference between Time and Plugwise MCP?

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

Time 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?

Time lists 9 tools with 3 views and 90,185 GitHub stars. Plugwise MCP lists 6 tools with 2 views and 2 GitHub stars.

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

Time vs Plugwise MCP

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

Time

Other Tools and Integrations · Local stdio

Quality: 88/100 (Excellent) | Auth: No auth required

Plugwise MCP

Other Tools and Integrations · Local stdio

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

Verdict Summary: Choose Time 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 Time when:

You need dedicated capabilities in the Other Tools and Integrations domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: create_entities, create_relations, add_observations.

Explore Time 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.
Primary tools included: Automatic Plugwise hub discovery, Thermostat, switch, and smart plug control, Temperature, preset, and schedule management.

Feature & Specification Comparison

Specification	Time VerifiedOther Tools and Integrations	Plugwise MCP Tommertom Other Tools and Integrations
Summary	Time and timezone conversion capabilities.	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

Time Tools (9)

create_entities

Create multiple new entities in the knowledge graph

create_relations

Create multiple new relations between entities in the knowledge graph. Relations should be in active voice

add_observations

Add new observations to existing entities in the knowledge graph

delete_entities

Delete multiple entities and their associated relations from the knowledge graph

delete_observations

Delete specific observations from entities in the knowledge graph

delete_relations

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

Time Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "time": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-memory"
      ]
    }
  }
}

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

Time 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 Time 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 Time More alternatives to Plugwise MCP Other Tools and Integrations category hub