Guide · Linux · X11 · Wayland
Remote mouse for Linux: your phone, Wayland included
Most phone-mouse apps stop at X11. MouseOS drives GNOME and KDE Plasma on Wayland too: trackpad, keyboard, the screen, copy-paste and media keys, from your phone, over your network.
In short: install the .deb or .rpm, open MouseOS on your phone, click ALLOW once. Free, on X11 and Wayland alike, on Ubuntu, Debian, Mint, Fedora, openSUSE and Raspberry Pi OS. No server between the phone and the computer.


Install MouseOS on Linux
- Download the .deb (Ubuntu, Debian, Mint;
arm64for Raspberry Pi OS) or the .rpm (Fedora, openSUSE) and install it with your package manager. The package grantsuinputfor Wayland and starts MouseOS with your desktop session. - Open MouseOS, or log in again. On Wayland without the package (a build of your own), click ALLOW CONTROL and enter your password once (details below). On X11 there's nothing to allow.
- Open MouseOS on the phone, same network. Click ALLOW on the computer for that phone. Done.
No mouse on the computer? A Raspberry Pi over SSH
Everything above needs no clicking. Install the package, reboot (or log in again): MouseOS is running in the desktop session. Then, over SSH or from any terminal on it:
mouseos allow --next 2m # the first phone to show up in two minutes is let in
mouseos status # name, address, permission, phones
mouseos list # linked, waiting, remembered
mouseos forget <phone> # it will ask again
These talk to the running app from this computer only: nothing on the network can reach them. From the first phone on, the phone is the mouse, including for the ALLOW button of the next one.
X11 or Wayland: how the input gets in
| Session | How input gets in |
|---|---|
| X11 | XTest: pointer, buttons, both scroll axes, Unicode typing in any layout. |
| Wayland | A virtual mouse and keyboard through uinput, seen by the compositor like real hardware. ALLOW CONTROL runs one pkexec step: it adds a udev rule tagging /dev/uinput with uaccess, so access for the signed-in user only, and loads the module at boot. |
Want to do it by hand instead? The app shows the three commands it would run. Volume goes through PipeWire or PulseAudio; media keys reach whatever player is in front.
Ports and network
- Clicks, keys and status: WebSocket on TCP 53317. Pointer and scroll: UDP 53318, accepted only from a phone you allowed.
- Discovery: mDNS plus a UDP beacon, so no IP to type. If your firewall blocks it, open those two ports for your LAN, or type the address the app shows.
- No server in between. What you do never leaves your network.
Frequently asked questions
Does it work on Wayland?
Yes. Wayland doesn't let apps move the pointer, so MouseOS uses a virtual input device (uinput) like a real mouse and keyboard. The package sets it up; a build of your own asks you to click ALLOW CONTROL once and enter your password.
Which distributions?
64-bit Linux, x86_64 and arm64: a .deb for Ubuntu, Debian, Mint and Raspberry Pi OS (Ubuntu 22.04, Mint 21, Debian 12 and later), an .rpm for Fedora and openSUSE.
Can I use my phone as a remote mouse on Ubuntu or Linux Mint?
Yes. Install the .deb, open MouseOS on the phone on the same network, and allow that phone once on the computer. It works on Ubuntu 22.04 and Linux Mint 21 or later, on X11 and Wayland.
Does it work on a Raspberry Pi, or a computer with no mouse?
Yes. The arm64 .deb runs on Raspberry Pi OS 64-bit (Pi 4, 5, 400). The package starts MouseOS with every desktop session, and mouseos allow --next over SSH lets the first phone in, with no mouse needed on the computer.
Which ports does it use?
TCP 53317 (WebSocket for clicks, keys and status) and UDP 53318 (pointer and scroll), on the local network only. Discovery uses mDNS and a UDP beacon.
Does MouseOS collect what I do?
No. What you do with the mouse and keyboard never leaves your network. The app only sends anonymous usage counts, and you can turn them off.