Skip to content

apiarya/wemo-mcp-server

v1.3.1 Breaking

This release includes breaking changes for platform teams planning a safe upgrade.

✓ No known CVEs patched
Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

Summary

AI summary

Fixed cache usage on server restart, ensuring device lookup tools reconnect without forced rescan and removing misleading key count in list_devices response.

Full changelog

Bug Fixes

🐛 Cache not used after server restart

All device-lookup tools now auto-reconnect to devices using the persistent JSON cache on restart — no forced rescan needed. Affects get_device_status, control_device, rename_device, and get_homekit_code.

🐛 list_devices ignored file cache on restart

list_devices now falls back to ~/.wemo_mcp_cache.json when in-memory cache is empty, showing all known devices immediately after restart.

🐛 Misleading cache_keys count in list_devices response

Removed the raw internal key count (always 2× device_count due to name+IP dual-indexing) that caused AI assistants to report a false 'discrepancy'. Only device_count is now returned.


Full Changelog: https://github.com/apiarya/wemo-mcp-server/blob/main/CHANGELOG.md

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

Track apiarya/wemo-mcp-server

Get notified when new releases ship.

Sign up free

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 →

Beta — feedback welcome: [email protected]