io.github.jaimenbell/desktop-mcp
io.github.jaimenbell/desktop-mcp
Is the io.github.jaimenbell/desktop-mcp MCP server down? Yes. It has given no valid answer since 2026-10-17: install failed.
Windows desktop-control MCP server: screenshot, window mgmt, mouse/keyboard input, recording.
install failed down since 2026-10-17 · probed 2026-11-14 · unchanged since 2026-10-31
And because you require desktop-mcp==0.1.1, we can conclude that your requirements are unsatisfiable. hint: Wheels are available for `pywin32` (v312)
- Run it
- uvx desktop-mcp@0.1.1 (stdio, probed in a container with the network off)
- Host
- pypi.org
- Repository
- https://github.com/jaimenbell/desktop-mcp
- Registry
- active, updated 2026-07-24 · registry entry
Compare this server with others.
More servers
Other registry entries on pypi.org, the ones next to this name; all of them.
- Nexus-MCP io.github.jaggernaut007/nexus-mcp · alive
- memo io.github.jagoff/memo · crashed on start
- SEC Intelligence io.github.jahanv01/sec-intelligence-mcp · needs network
- io.github.jaimenbell/bus-mcp · alive
- io.github.jaimenbell/discord-mcp · alive
- io.github.jaimenbell/github-mcp · alive
- io.github.jaimenbell/mcp-factory · needs env
- io.github.jaimenbell/rag-mcp · alive
Servers that mention desktop.
- Remote Desktop Commander app.desktopcommander/remote-desktop-commander · needs auth
- shelf-smoke — url smoke / headless QA co.kymac.shelf/shelf-smoke · no DNS
- MCP OAuth Connect com.gfbytes/mcp-oauth-connect · not found
- MyClawn Computer com.myclawn/desktop · needs auth
- RepoGates com.repogates/repogates · needs auth
- SignatureForever com.signatureforever/email-signatures · alive
- ScreenshotMCP io.github.AgentForge-Labs/site-screenshot · alive
- Agent Failure Archive io.github.HanbeenMoon/agent-failure-archive · TLS error
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
- No valid answer since 2026-10-17, in every probe since then.
- npx or uvx could not install the package. The package name in the registry entry is wrong, the package is not published, or the install needs a build step.