WeMo MCP Server
Control WeMo smart home devices through AI assistants using natural language.
mcp-name: io.github.apiarya/wemo
Table of Contents
- Overview
- Prerequisites
- Quick Start
- Connect
- Configuration
- MCP Tools
- scan_network
- list_devices
- get_device_status
- control_device
- rename_device
- get_homekit_code
- get_cache_info
- clear_cache
- get_configuration
- MCP Capabilities
- Resources
- Prompts
- Elicitations
- How It Works
- Local Control Signal Flow
- Feature Comparison
- Development
- Contributing
- License
- Acknowledgments
Overview
Seamlessly integrate WeMo smart home devices with AI assistants through the Model Context Protocol. Built on pywemo, this server enables natural language control of your WeMo devices with intelligent multi-phase discovery.
Example Usage
Control WeMo devices through AI assistants with natural language - just ask in plain English!
"Goodnight" — one command turns off every device in the house
Key Features
- 🔍 Smart Discovery - Multi-phase scanning (UPnP/SSDP + network ports) with 100% reliability
- ⚡ Fast Scanning - Parallel probes with 60 concurrent workers (~23-30s for full subnet)
- 🎛️ Full Control - On/off/toggle/brightness control for all device types
- ✏️ Device Management - Rename devices and extract HomeKit setup codes
- 📊 Real-time Status - Query device state and brightness
- 💾 Smart Caching - Persistent device cache with 1-hour TTL survives restarts
- 🔧 Configurable - YAML config files + environment variables for all settings
- 🔄 Auto-Retry - Automatic retry with exponential backoff for network errors
- 🛡️ Error Handling - Detailed error messages with actionable suggestions
- 🔌 Universal - Works with any MCP client (Claude, VS Code, Cursor, etc.)
- 📡 MCP Resources - Live device state via
devices://anddevice://{id}URIs - 💬 MCP Prompts - Built-in guided prompts: discover, status report, scene control, troubleshoot
- 🗣️ MCP Elicitations - Interactive clarification when subnet or device name is ambiguous
