Skip to content

apiarya/wemo-mcp-server

v1.1.0 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

Minor fixes and improvements.

Full changelog

v1.1.0 - Repository Migration 🏠

🎉 New Home for WeMo MCP Server

The WeMo MCP Server now has its own dedicated repository!

New Repository: https://github.com/apiarya/wemo-mcp-server

This move follows MCP ecosystem best practices and significantly improves discoverability for users finding the server through the official MCP Registry.

What Changed

Repository & Infrastructure

  • ✅ Migrated from qrussell/wemo-ops-center/mcp monorepo
  • ✅ All documentation and URLs updated to new repository
  • ✅ CI/CD pipeline configured for standalone repo
  • ✅ MCP Registry metadata updated with new location
  • ✅ Simplified versioning (no more mcp-v* tags, just v*)

Documentation

  • ✅ All image URLs and links updated
  • ✅ Installation instructions verified
  • ✅ Contributing guidelines updated
  • ✅ Issue tracking moved to new repository

No Breaking Changes

  • ✅ Package name remains: wemo-mcp-server
  • ✅ Installation command unchanged: pip install wemo-mcp-server
  • ✅ All MCP tools function identically
  • ✅ Configuration compatibility maintained

For Users

No action needed! Just install or upgrade as usual:

# Via pip
pip install --upgrade wemo-mcp-server

# Via uvx (recommended)
uvx wemo-mcp-server@latest

For Contributors

Please submit issues and PRs to the new repository:

  • Issues: https://github.com/apiarya/wemo-mcp-server/issues
  • Pull Requests: https://github.com/apiarya/wemo-mcp-server/pulls

Why This Matters

MCP Registry Compliance

The MCP Registry requires base repository URLs without path components. The previous URL (/tree/main/mcp) caused validation failures.

Better User Experience

Users discovering the server through the MCP Registry now land directly on MCP documentation instead of the desktop app README.

Industry Standard

This aligns with patterns used by major MCP servers:

Related Projects

The WeMo MCP Server complements the WeMo Ops Center desktop and server applications for managing WeMo devices.

Installation

# PyPI
pip install wemo-mcp-server

# uvx (recommended for MCP)
uvx wemo-mcp-server

Quick Start

Add to your MCP client configuration:

{
  "mcpServers": {
    "wemo": {
      "command": "uvx",
      "args": ["wemo-mcp-server"]
    }
  }
}

Full Changelog

See CHANGELOG.md for complete version history.


Thanks to @qrussell for the collaboration and support in making this migration happen! 🙏

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]