apiarya/wemo-mcp-server

v1.4.0 Feature

This release adds 2 notable features for engineering teams evaluating rollout.

Published 3mo MCP Browser & Automation

View tool

✓ No known CVEs patched

Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

Summary

AI summary

Added MCP resources and AI assistant slash‑command prompts.

Full changelog

What's New in v1.4.0

✨ MCP Resources

Two new resources for direct device data access:

devices:// — Static JSON index of all cached devices (falls back to persistent cache on restart)
device://{device_id} — Live device state by name or IP; supports URL-encoded names (e.g. device://Master%20Bed%20346)

✨ MCP Prompts

Four slash-command prompts for AI assistants:

discover-devices — Scan network and summarise all found WeMo devices
device-status-report — Report status of all known devices (pre-populated with cached names)
activate-scene — Control devices for preset lighting scenes (movie night, bedtime, wake up, away, full brightness)
troubleshoot-device — 4-step diagnostic sequence for a named device

🐛 Fixed

URL-encoded device IDs in resource template now decoded correctly (fixes device://Name%20With%20Spaces)

🔧 Improved

CI now runs all 128 unit tests (was 30)

View diff on GitHub

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Share on X Share on Bluesky

Track apiarya/wemo-mcp-server

Get notified when new releases ship.

About apiarya/wemo-mcp-server

![wemo-mcp-server MCP server](https://glama.ai/mcp/servers/@apiarya/wemo-mcp-server) 🪟 - Control WeMo smart home devices via AI assistants using natural language. Built on pywemo for 100% local control — no cloud dependency. Supports dimmer brightness, device rename, HomeKit codes, and multi-phase discovery.

All releases →