Building an MCP Server for Linux Desktop GUI Automation on Wayland

When I started working on AI agent tooling, I hit a wall: there's no clean way to automate GUI interactions on Wayland. X11 had xdotool and DISPLAY=:99 — Wayland killed all of that, by design. No global input injection, no screen grabbing without portal authorization dialogs. So I built kwin-mcp , an MCP server that gives AI agents full GUI automation capabilities on Linux desktops, running in a completely isolated KWin Wayland session. The Problem Wayland's security model blocks the automation patterns we took for granted on X11. There's no equivalent of pointing tools at a virtual display. XDG RemoteDesktop portals require interactive user authorization — useless for headless automation. And most Wayland compositors don't expose any input injection API at all. The Solution: Triple Isolation kwin-mcp creates three layers of isolation for each session: Private D-Bus bus ( dbus-run-session ) — no interference with host services Virtual Wayland compositor ( kwin_wayland --virtual ) — no