vnc_click
Click at specified coordinates
LABSCO SUMMARY
A hand and an eye on a remote desktop: coordinates in, screenshot out.
There is no element model here — nothing queries the screen for a button — so every action is a coordinate the caller worked out from the previous vnc_screenshot, and the loop is screenshot-driven by construction. What that buys is reach: an installer, a native desktop app or a BIOS-era dialog is as addressable as a web page, which no browser-based tool can say. vnc_type_multiline and the delay on vnc_screenshot are the two details that keep the loop from being one call per line.
What it is
A VNC input server, six tools that send mouse and keyboard events to a remote screen and read it back as a screenshot.
What you get
- vnc_click at x and y with a button choice and a double-click flag, and vnc_move_mouse to position the pointer without clicking
- vnc_type_text for a single string, with an option to press Enter after it, and vnc_type_multiline to send several newline-separated lines in one call
- vnc_key_press for a key or a key combination, which is what covers shortcuts and dialogs that have no clickable target
- vnc_screenshot with a delay parameter, so the capture can be taken after the screen has settled rather than mid-redraw
Requirements
A reachable VNC server, and screen coordinates to act on: the tools address the screen by x and y rather than by element. MIT licensed.
Setup effort
One command plus credentials — npm install -g @hrrrsn/mcp-vnc, then supply credentials
USE CASES
01
Getting through a desktop installer nothing else can reach
Take a screenshot to see the current dialog, click the button at its coordinates, and use key combinations for the steps that have no clickable target.
02
Entering a block of text into a remote editor
Put the cursor where the text belongs, send all the lines in one call rather than one per line, then capture the screen to confirm it landed intact.
6 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
vnc_key_press
Press a key or key combination
vnc_move_mouse
Move mouse to specified coordinates
vnc_screenshot
Take a screenshot of the current screen
vnc_type_multiline
Type multiple lines of text, separated by newlines
vnc_type_text
Type text string
BEFORE YOU INSTALL
What to know first
Tools you get
6 tools when we connected. Five tools act on the real machine with no confirmation or undo; only vnc_screenshot reads. There is no scrolling, drag, clipboard or file transfer.
Requires
VNC_PASSWORD in your environment
CONTEXT COST
Light Standing cost
Rated by the size of the 6 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npm install -g @hrrrsn/mcp-vncMCP Clients
Claude Desktop — global install
CLAUDE DESKTOP — GLOBAL INSTALL · JSON
{
"mcpServers": {
"vnc-controller": {
"type": "stdio",
"command": "mcp-vnc",
"env": {
"VNC_HOST": "192.168.1.100",
"VNC_PORT": "5900",
"VNC_PASSWORD": "<YOUR_VNC_PASSWORD>"
}
}
}
}Claude Desktop — from source
CLAUDE DESKTOP — FROM SOURCE · TERMINAL
git clone https://github.com/hrrrsn/mcp-vnc
cd mcp-vnc
npm install
npm run buildCLAUDE DESKTOP — FROM SOURCE · JSON
{
"mcpServers": {
"vnc-controller": {
"type": "stdio",
"command": "node",
"args": [
"<YOUR_PATH_TO_MCP_VNC>/dist/index.js"
],
"env": {
"VNC_HOST": "192.168.1.100",
"VNC_PORT": "5900",
"VNC_PASSWORD": "<YOUR_VNC_PASSWORD>"
}
}
}
}<YOUR_PATH_TO_MCP_VNC> is the absolute path of your clone, and set VNC_HOST, VNC_PORT and VNC_PASSWORD for the machine you want to control.
