clickLABSCO SUMMARY
Coordinates in, desktop moves.
It is a thin layer over the operating system rather than an integration with any one application, so what it can reach is whatever a person could reach with a mouse and keyboard — and it needs the screen to itself while it does.
What it is
A desktop automation server written in Go and running over stdio. It exposes mouse, keyboard and screen control as tools: clicking at coordinates, moving the cursor with or without animation, typing with optional per-character delays, pressing key combinations, and capturing screenshots.
What you get
- Clicks at coordinates you name, with right click and double click each their own tool
- The cursor moved with smooth animation or instantly, and its current position read back
- Text typed at the cursor position, with a configurable delay between characters
- Individual keys and key combinations pressed
- A full-screen screenshot captured to a file, and the screen dimensions read
Requirements
Go, to build the binary, plus whatever your operating system requires before an application may control the mouse, keyboard and screen. It runs over stdio with no configuration beyond the binary path.
Setup effort
Build from source — git clone https://github.com/dmahlow/gceu_workshop_mcp_live.git
USE CASES
01
Driving an application that has no API
Screenshot to see the state, move to the control, click it — the loop for software that was never meant to be automated.
02
Filling in a form in a desktop app
Type into each field and tab between them, with delays where the app cannot keep up.
03
Capturing what is on screen right now
A full-screen capture saved to a file, with the screen dimensions to interpret it against.
04
Repeating a click sequence you keep doing by hand
The same coordinates, the same order, without the drift of doing it manually.
05
Working out where things are before automating them
Read the screen size and the current cursor position, and capture the screen to measure against.
9 tools
Listed in project docs. Your client may show a different list.
right_clickdouble_clickmove_mouseget_mouse_positiontype_textpress_keytake_screenshotget_screen_sizeBEFORE YOU INSTALL
What to know first
Tools you get
9 tools named in the project's documentation.
Requires
- Go 1.23.0 or later
- A C compiler (GCC, or Xcode Command Line Tools on macOS)
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
Have Go 1.23.0 or later and a C compiler installed (the robotgo library builds with cgo: GCC, or Xcode Command Line Tools on macOS)
TERMINAL
git clone https://github.com/dmahlow/gceu_workshop_mcp_live.git
cd gceu_workshop_mcp_live
go mod download
go mod tidy
go build -o mcp-server ./cmd/mcp-serverOr, if the Task runner is installed: task build.
Add the mcpServers block to your client, pointing command at the mcp-server binary just built
MCP Clients
Any MCP client
ANY MCP CLIENT · JSON
{
"mcpServers": {
"desktop-automation": {
"command": "<YOUR_PATH_TO_MCP_SERVER>"
}
}
}
