Wemo
Let your coding agent discover and control WeMo plugs and lights on your LAN without writing custom UPnP scripts.
Overview
io.github.apiarya/wemo is a Build-phase MCP server that lets AI agents discover and control WeMo smart-home devices on your local network.
What is this MCP server?
- Discover WeMo devices on the local network from MCP tool calls
- Toggle power and adjust brightness on supported switches and bulbs
- Manage HomeKit pairing codes from the same stdio MCP server
- PyPI package wemo-mcp-server v1.4.1 with stdio transport for Claude Code and Cursor
- GitHub-hosted server you run locally—no cloud relay required for device control
- Catalog version 1.4.1 on PyPI identifier wemo-mcp-server
- Transport: stdio
- Source repository: github.com/apiarya/wemo-mcp-server
What problem does it solve?
Hooking WeMo discovery, toggles, and brightness into an agent workflow usually means brittle custom networking code instead of a ready MCP tool surface.
Who is it for?
Builders running local MCP who want quick agent-driven control of WeMo hardware during prototyping or personal automation.
Skip if: Teams that need enterprise smart-building management, non-WeMo ecosystems only, or cloud-only device control without a LAN-capable host.
What do I get? / Deliverables
After you register the stdio server, your agent can call MCP tools to operate WeMo devices and manage HomeKit-related codes from the same session as your code.
- Runnable stdio MCP server wired into your agent config
- Agent-callable tools for WeMo discovery, power, brightness, and HomeKit code workflows
Recommended MCP Servers
Journey fit
Solo builders add smart-home control while wiring automations and side projects that touch physical devices. Integrations is the shelf for MCP bridges to third-party hardware and local network services agents can call from the IDE.
How it compares
Local IoT integration MCP, not a cloud infra provisioner or ASPM security server.
Common Questions / FAQ
Who is io.github.apiarya/wemo for?
It is for solo builders and developers who use Claude Code, Cursor, or similar agents and want MCP-native control of WeMo devices on their network.
When should I use io.github.apiarya/wemo?
Use it during Build when you are integrating home or lab hardware into agent workflows—discovery, toggles, brightness, or HomeKit code tasks—without writing a custom UPnP client.
How do I add io.github.apiarya/wemo to my agent?
Install the PyPI package wemo-mcp-server (1.4.1), configure an MCP stdio entry pointing at that server in Claude Code or Cursor, and ensure the host can reach WeMo devices on your LAN.