Remote Pc MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 149 installs a week from pypi. Last commit 19 Oct 2026.
Drive a PC over MCP: shell, files, processes, system stats, screenshots, mouse and keyboard.
We read the source, 1 d ago · rules 995398eba69f
A value the model can set ends up inside a file or shell call. That is not a flaw by itself — for a terminal server it is the job — but it is where things go wrong when it is not.
proc = subprocess.Popen(command, shell=True, stdout=out, stderr=err, cwd=working_dir)
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
result = subprocess.run(
shell=True,
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
That is not a flaw by itself — but it is where things go wrong when it is not the job. We re-read this code on every release. Watch it and you hear from us the day another one appears.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add remote-pc-mcp -e 'REMOTE_PC_MCP_TOKEN=<REMOTE_PC_MCP_TOKEN>' -- uvx remote-pc-mcp
{
"mcpServers": {
"remote-pc-mcp": {
"command": "uvx",
"args": [
"remote-pc-mcp"
],
"env": {
"REMOTE_PC_MCP_TOKEN": "<REMOTE_PC_MCP_TOKEN>"
}
}
}
}
[mcp_servers.remote-pc-mcp]
command = "uvx"
args = ["remote-pc-mcp"]
env = { REMOTE_PC_MCP_TOKEN = "<REMOTE_PC_MCP_TOKEN>" }
{
"mcpServers": {
"remote-pc-mcp": {
"command": "uvx",
"args": [
"remote-pc-mcp"
],
"env": {
"REMOTE_PC_MCP_TOKEN": "<REMOTE_PC_MCP_TOKEN>"
}
}
}
}
{
"servers": {
"remote-pc-mcp": {
"type": "stdio",
"command": "uvx",
"args": [
"remote-pc-mcp"
],
"env": {
"REMOTE_PC_MCP_TOKEN": "<REMOTE_PC_MCP_TOKEN>"
}
}
}
}
Put your own value in place of
<REMOTE_PC_MCP_TOKEN> (Bearer token clients must present. Treat as a root-equivalent credential on the host).
The author’s registry entry marks it as required.
Optional settings from the registry entry, left out of the block above:
REMOTE_PC_MCP_HOST (Interface to bind (default 0.0.0.0)), REMOTE_PC_MCP_PORT (Port to listen on (default 8765)).
Control Windows desktop via MCP: mouse, keyboard, screenshots, clipboard, and apps.
Securely use files, terminals, screenshots and processes on computers you pair with ReMCP.
Control your computer with screenshots, mouse, and keyboard automation.
Open-source Windows MCP server for AI assistants. File, clipboard, screenshot, process & power mgmt.
Windows desktop-control MCP server: screenshot, window mgmt, mouse/keyboard input, recording.
MCP server for web page and cross-platform system screenshots (macOS, Linux, Windows)
Structured Windows state for AI agents: processes, windows, UI trees. No screenshots.
Inspect and drive WPF apps: trees, bindings, screenshots, mouse dragging and touch gestures.
Answers built from our own checks of this server.