Remote Pc MCP server

remote-pc-mcp

Expose any PC's capabilities — shell, filesystem, background processes, system stats, screenshots, UI control, and file transfer — to any MCP client (Claude Desktop, Claude Code, Cursor, Cline, Continue, Windsurf, custom agents — anything that speaks the Model Context Protocol) over streamable HTTP.

Drop it on any machine you want to drive remotely: a home server, a desktop, a build/CI box, a media server, a workstation, a Raspberry Pi. From a separate machine, your AI agent of choice can run commands on it, manage files, launch and monitor background jobs, take screenshots, and drive the desktop UI.

The transport is the mcp SDK's streamable HTTP (stateless_http=True), so a server restart does not break already-connected clients. Each request is self-contained — there is no in-memory session to go stale.

⚠️ shellexec runs arbitrary commands on the host as the user that started the server.** The bearer token is a root-equivalent credential. See Security before exposing the server.

Tools

Requirements

• Python 3.10+
• Windows 10/11, or Linux with systemd (for autostart)

Install

On the machine you want to control:

git clone https://github.com/raghibrm/remote-pc-mcp
cd remote-pc-mcp
cp .env.example .env

Set a strong token in .env:

REMOTE_PC_MCP_TOKEN=your-long-random-token-here

Generate one:

# Windows
python -c "import secrets; print(secrets.token_hex(32))"

# Linux / macOS
openssl rand -hex 32

Then run the installer:

# Windows
install.bat

# Linux
chmod +x install.sh
./install.sh

That's it — one command. The installer:

• installs Python dependencies
• registers the server to launch hidden on every login (Startup-folder shortcut on Windows, systemd user unit on Linux)
• starts it now
• supervises it with exponential backoff on crash (5→10→20→40→60 seconds, resets after 5 minutes of uptime)
• survives reboots — set once, runs forever

Verify it's up

curl http://localhost:8765/health
# {"status":"ok","server":"remote-pc-mcp","version":"0.5.0"}

When to rerun the installer

install.bat / install.sh are idempotent and self-healing. Rerun any time after:

• You move the repo to a different folder
• You reinstall or upgrade Python to a different path
• You rebuild the machine and want to restore autostart

For day-to-day operation you never need to think about it.

After a reboot

Shortened. The full README is on GitHub.