"smart" matching MCP servers:

Enables AI agents to interact with IoT device data from a smart city, including public lighting, water, and gas meters. Supports querying and management via the Model Context Protocol.

An MCP server that lets an MCP client control IKEA TRÅDFRI smart plugs paired to a DIRIGERA hub via its local REST API.

Enables AI assistants to control a Homey Pro smart home hub, create automation flows from natural language, and query device and energy history.

MCP server for the entire Shelly smart-home ecosystem, enabling local-first control, automation, and energy monitoring of Shelly devices with cloud fallback.

Provides a unified MCP interface for smart home automation, enabling device discovery, state management, energy optimization, and policy-aware plan validation across multiple home automation protocols.

Enables remote control of SwitchBot Plug Mini smart plugs via the SwitchBot Open API, including listing devices, checking power status, and turning on/off or toggling plugs through MCP tools, secured by GitHub OAuth.

Enables natural language control of Loxone smart home systems, including lighting, audio, climate, and environmental monitoring, through MCP-compatible clients.

Enables Claude AI to control and manage Homey Pro smart home devices, flows, and analytics through natural language.

Pay-per-call MCP server for SMARD day-ahead electricity prices (DE-LU, 15-minute resolution) on Base mainnet via x402.

Enables voice control of Nest thermostats from a Pebble Index ring via MCP, using Google's Smart Device Management API to list thermostats, report status, and adjust temperature, mode, eco, and fan settings.

Connects Claude and other MCP clients to myGEKKO building controllers via the official Query API, enabling natural-language queries and control of smart-home devices. It is read-only by default, with write actions available only through explicit opt-in and safety policies.

Connects MCP clients such as Claude to a NIBE myUplink heat-pump account, letting users list systems and devices, read sensor values and common parameters, check alarms, view smart-home zones, and write settings where scopes allow. Handles the OAuth2 authorization-code and client-credentials flows, refreshing tokens automatically while keeping credentials in a local .env file.