Ext Ops Panel
Open dashboard
Comparison

desktop-act vs kwin-mcp

kwin-mcp is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑16.

desktop-act is a plugin bundle for AI coding tools published by Lifecycle Innovations Limited. Marketplaces we read that list it: 1 (Community GitHub marketplaces). kwin-mcp is a plugin bundle for AI coding tools published by Byeonghoon Yoo. No marketplace we read lists it any more. As of our marketplace pass on 2026-10-18. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplacedesktop-actkwin-mcp
Community marketplace lifecycle-innovations-limited/claude-ops Listed
Version: 0.2.0
Forks (GitHub): 64
Stars (GitHub): 546
Not marked · First seen
Not listed
Community marketplace vibeprogramm/kwin-mcp Not listed Removed on 2026-10-16
Version: 0.9.0
Forks (GitHub): 0
Stars (GitHub): 2
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

desktop-act vs kwin-mcp
Factdesktop-actkwin-mcpno longer listed ·
Marketplaces that list it (differs)10
Stars (GitHub) (differs)5462
Forks (GitHub) (differs)640
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (kwin-mcp)
TransportNot statedNot stated
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)32
LicenceMITMIT
Repository (differs)github.com/lifecycle-innovations-limited/claude-opsgithub.com/vibeprogramm/kwin-mcp
Changes in the last 7 days (differs)24
First seen (differs)2026-10-132026-10-14

Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.

What to use instead of kwin-mcp

Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.

  • kwin-mcp

    KDE Plasma 6 Wayland GUI automation for AI agents: 30 tools (EIS input, screenshots, AT-SPI2).

    by VibeProgramm · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • ultranix-mcp

    Secure Linux desktop automation - input, screen/OCR/vision, AT-SPI2 UI tree, window, clipboard

    by jxoesneon · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • agentfenster

    Windows GUI automation on a hidden second desktop, driven from Claude Code over MCP.

    by agentfenster.com · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • UIAutomationMcp

    Windows UI Automation MCP server for desktop inspection and element lookup. Windows only.

    by trsdn · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • deskbrid io.github.coe0718/deskbrid

    Linux automation. 125 MCP tools: windows, input, screenshots, clipboard, print, AT-SPI. 9 DEs.

    by coe0718 · MCP server

    Listed on: Official MCP Registry · Describes a similar job

  • hammerspoon io.github.mobabur94/hammerspoon

    macOS automation via Hammerspoon — 75 tools for windows, Spaces, audio, Bluetooth, and more

    by mobabur94 · MCP server

    Listed on: Official MCP Registry · Describes a similar job

Its card, with similar plugins by marketplace

What each says it does

desktop-act

In its own words, on Community GitHub marketplaces:

Computer-use MCP companion for /ops:desktop — screenshot, click, type, multi-desktop pool, autonomous act loop. Co-installed with the ops plugin.

kwin-mcp

In its own words, on Community GitHub marketplaces:

Bundles the kwin-mcp MCP server (uvx kwin-mcp) plus the kwin-desktop-automation skill that teaches session-mode selection, the observe-act-verify loop, US-QWERTY vs Unicode typing, and platform pitfalls (surface-local coordinates, QMenu invisibility, EIS edge limits, clipboard opt-in).

How to run each

desktop-act As a Claude Code plugin

Claude Code
/plugin marketplace add lifecycle-innovations-limited/claude-ops
/plugin install desktop-act@ops-marketplace

kwin-mcp

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: desktop-act · What it can do: kwin-mcp · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built