pickfit

BrowseMCP servers

niri-computer-use

MCP server letting AI agents observe and drive a niri Wayland desktop.

Tested on Linux

Use it

Linux x86_64

You need first

  • Runtimes: Rust 1.99 or newer
  • System packages: grim, loginctl, notify-send, libxkbcommon-dev
  1. Download install script only

    curl -fsSL https://github.com/ayagmar/niri-computer-use/releases/latest/download/install.sh -o /tmp/ncu-install.sh && ls -l /tmp/ncu-install.sh
  2. Fetch and extract libxkbcommon locally

    mkdir -p ~/.local/lib ~/.local/debxkb && curl -fsSL https://ftp.debian.org/debian/pool/main/libx/libxkbcommon/libxkbcommon0_1.7.0-2_amd64.deb -o /tmp/libxkbcommon0.deb && dpkg-deb -x /tmp/libxkbcommon0.deb ~/.local/debxkb && find ~/.local/debxkb -name "*.so*" -ls && cp -P ~/.local/debxkb/usr/lib/x86_64-linux-gnu/libxkbcommon.so* ~/.local/lib/ && ls -l ~/.local/lib/
  3. Retry install with local lib path

    export LD_LIBRARY_PATH="$HOME/.local/lib:${LD_LIBRARY_PATH:-}" && NCU_REGISTER=0 sh /tmp/ncu-install.sh

Check that it works

LD_LIBRARY_PATH="$HOME/.local/lib:${LD_LIBRARY_PATH:-}" ~/.local/bin/niri-computer-use --version

The output should contain “niri-computer-use 0.1.5”.

First thing to try

LD_LIBRARY_PATH="$HOME/.local/lib:${LD_LIBRARY_PATH:-}" ~/.local/bin/niri-computer-use status

Add it to your agent

claude mcp add niri-computer-use -- $HOME/.local/bin/niri-computer-use serve
JSON for Claude Desktop, Cursor and other clients
{
  "mcpServers": {
    "niri-computer-use": {
      "command": "sh",
      "args": [
        "-c",
        "exec \"$HOME/.local/bin/niri-computer-use\" serve"
      ]
    }
  }
}

Run niri-computer-use status to check that the server can reach your niri desktop, then add it to your MCP client.

What it does

These come from the README; pickfit didn’t check them one by one.

  • See and control your niri desktop
    Not tested
  • Take screenshots and send key presses and clicks
    Not tested
  • Act on on-screen elements by their accessible name
    Not tested
  • Manage window focus and layout
    Not tested

How far pickfit got

Linux x86_64

  1. Installs
  2. Connects
  3. A tool call works
  4. Works offline

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

Linux x86_64

An MCP client called one of its tools

  • Replayed from scratch
  • Works offline
  • Checked on 30 Oct 2026
  • Version 0.1.5

An MCP client handshake over stdio listed 17 tools, and a call to status returned a result.

Differences the test machine hit

  • README: curl -fsSL https://github.com/ayagmar/niri-computer-use/releases/latest/download/install.sh | sh installs the release binary
    In the test: Manually fetched libxkbcommon0_1.7.0-2_amd64.deb from ftp.debian.org, extracted with dpkg-deb -x to ~/.local/debxkb, copied libxkbcommon.so.0* to ~/.local/lib, and ran the install script and every niri-computer-use invocation with LD_LIBRARY_PATH=$HOME/.local/lib
  • README: install script installs the release binary checked against its .sha256
    In the test: install.sh downloads a compiled binary tarball (niri-computer-use-0.1.5-x86_64-linux.tar.gz + .sha256) which was verified by checksum but cannot be read as a script

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.