io.github.qrussell/wemo
wemo-mcp-server
Is the io.github.qrussell/wemo MCP server down? No. Installed with mcp<2, it started and listed its tools on 2026-10-31.
Control WeMo smart home devices - discover, toggle, adjust brightness, and manage HomeKit codes
needs mcp<2 probed 2026-11-14 · unchanged since 2026-10-31
A plain install of the package stops at the import below. These tool definitions are from a second install with mcp<2, started in a container with the network off, on 2026-10-31.
MCP error -32000: Connection closed ModuleNotFoundError: No module named 'mcp.server.fastmcp'. This is mcp 2.x, where FastMCP was renamed to MCPServer (from mcp
- Run it
- uvx --with 'mcp<2' wemo-mcp-server@1.0.1 (stdio, probed in a container with the network off)
- Host
- pypi.org
- Reports itself as
- wemo-mcp-server 1.30.0
- Capabilities
- experimental, prompts, resources, tools
- Repository
- https://github.com/qrussell/wemo-ops-center
- Registry
- active, updated 2026-02-16 · registry entry
- Changes
- 2 recorded, reachable in 0 of them. A row is added when the result, the tool count or the cost changes.
Most expensive tools
Estimates with the o200k_base tokenizer.
| Tool | o200k estimate | Share of this server |
|---|---|---|
| control_device | 307 | 22 % |
| rename_device | 279 | 20 % |
| scan_network | 276 | 20 % |
| get_homekit_code | 259 | 18 % |
| get_device_status | 176 | 13 % |
Compare this server with others.
More servers
Other registry entries on pypi.org, the ones next to this name; all of them.
- io.github.q1023884985/visiongemma · needs env
- Task Checkpoint io.github.qddfxp/task-checkpoint-mcp · alive
- TAR Engine io.github.qingxuantang/tar-engine · needs args
- io.github.qkrehgk1-wq/mcp-korea-worklife · alive
- io.github.qso-graph/adif-mcp · alive
- io.github.qso-graph/cq-zones-mcp · alive
- io.github.qso-graph/darc-dok-mcp · alive
- io.github.qso-graph/dxe-mcp · alive
Servers that mention wemo or brightness or discover.
- Moveat app.wemoveat/moveat · needs auth
- io.github.apiarya/wemo · needs mcp<2
- ai.adoraads/beauty · alive
- AFMR Discovery ai.afmr/discovery · alive
- ai.astrofabric/mcp · not MCP
- Boolsai Grep ai.boolsai/grep · no DNS
- Orbit ai.buildwithorbit/orbit · alive
- China Marketing AI Intelligence MCP ai.chinamarketing/intelligence · needs auth
History
We add a row when the result changes. A server with no change keeps its last row.
| Probed | Result | Init | Tools | Claude | o200k |
|---|---|---|---|---|---|
| 2026-10-31 07:39 | needs mcp<2 | 1.4 s | 6 | 2.2k | 1.4k |
| 2026-10-17 06:19 | crashed on start |
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The package imports FastMCP from mcp.server.fastmcp. mcp 2.0, the Python SDK of 28 July 2026, renamed FastMCP to MCPServer, and the package asks for mcp with no upper bound, so a plain install (uvx, pip) gets mcp 2.x and the server stops at the import. Installed with mcp<2, it starts and lists its tools. The fix for the publisher: pin mcp<2 in the dependencies, for example mcp>=1.2,<2, and publish a new version, or move to MCPServer as the SDK's migration guide says. Until then, run it with uvx --with 'mcp<2'.
The cause and the fix, with the code before and after: ModuleNotFoundError: No module named 'mcp.server.fastmcp'