Enterprise DNA
M MCP Servers Developer low

apiarya/wemo-mcp-server

by Various

Control Wemo smart home devices through AI assistants using natural language.

A

MCP

apiarya/wemo-mcp-server

Added 1 June 2026

Overview

This server exposes Wemo smart home devices through the Model Context Protocol (MCP), enabling AI assistants to control lights, switches, and other Wemo devices via natural language commands. Users interact through an MCP client (like Claude Desktop) that translates requests into device actions.

Best for

Best for
Developers building AI assistants that need voice or text control of local Wemo home devices

Use cases

  • Turn on/off Wemo lights or switches via voice or chat prompts
  • Schedule device state changes through conversational AI workflows
  • Integrate Wemo control into agent-based automation pipelines

Notes

This server exposes Wemo smart home devices through the Model Context Protocol (MCP), enabling AI assistants to control lights, switches, and other Wemo devices via natural language commands. Users interact through an MCP client (like Claude Desktop) that translates requests into device actions.

0 stars on GitHub. Last updated 2026-05-04. Licensed MIT.

Use cases

  • Turn on/off Wemo lights or switches via voice or chat prompts
  • Schedule device state changes through conversational AI workflows
  • Integrate Wemo control into agent-based automation pipelines

Pros

  • Zero-config discovery of Wemo devices on the local network
  • Leverages existing MCP ecosystem for seamless AI assistant integration
  • Lightweight Python implementation with minimal dependencies

Cons

  • Requires local network access to Wemo devices (no cloud relay)
  • No authentication or access controls built in
  • Limited to devices that are already paired and on the same subnet

Indexed from awesome-mcp-servers-punkpeye and enriched against its public facts.

Pros

  • Zero-config discovery of Wemo devices on the local network
  • Leverages existing MCP ecosystem for seamless AI assistant integration
  • Lightweight Python implementation with minimal dependencies

Cons

  • Requires local network access to Wemo devices (no cloud relay)
  • No authentication or access controls built in
  • Limited to devices that are already paired and on the same subnet