Remote Pc MCP vs Clickr
A side-by-side look at the Remote Pc MCP and Clickr MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
C
ClickrOS AutomationClickr — macOS screen measurement and input control MCP for Claude Code. Screenshot any display, click any global coordinate, type into any application.49FairAuth: no auth requiredVerdict: choose Remote Pc MCP for os automation work as a local process; choose Clickr for os automation. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Remote Pc MCP when
- You need dedicated capabilities in the OS Automation domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
REMOTE_PC_MCP_TOKEN. - You want tools like
shell_exec, read_file, write_file.
CChoose Clickr when
- You need dedicated capabilities in the OS Automation domain.
- Its auth model fits you: No auth required.
- You want tools like
check_permissions, list_displays, list_windows.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | C Clickr | |
|---|---|---|
| Category | OS Automation | OS Automation |
| Quality signal | 55/100 · Good | 49/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | API key required | No auth required |
| Pricing | Free | Free |
| Required env vars | REMOTE_PC_MCP_TOKEN | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 6 | 1 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 15 | 19 |
| Full listing | View Remote Pc MCP | View Clickr |
Tools & capabilities
Remote Pc MCP tools 15
shell_execRun any shell command — returns stdout, stderr, exit coderead_fileRead a file as text or base64 (binary fallback)write_fileWrite text or binary content to a filelist_directoryList files and directories, optionally recursivesystem_infoOS, CPU, RAM, and GPU stats (NVIDIA GPUs via `nvidia-smi`; absent on non-GPU hosts)start_processStart a long-running command in the background — returns a PIDget_process_outputPoll stdout/stderr of a background process by PIDkill_processTerminate a process by PIDdownload_fileDownload a URL directly to this machinetake_screenshotCapture the primary display — returns base64-encoded PNGclickClick at screen coordinates `(x, y)` — left / right / middle, single or multi-clickmove_mouseMove cursor to `(x, y)`, optionally animated- +3 more on the listing page
Clickr tools 19
check_permissionsReport Accessibility / Screen Recording status and how to fix themlist_displaysEvery display's position and size in global pointslist_windowsOn-screen windows with app, title, and boundslist_appsRunning applications with pid and bundle idfind_elementsLocate controls as text with exact click coordinates — prefer over screenshotread_textOn-device OCR of a region; returns text, no imageelement_atDescribe the accessibility element at a coordinatescreenshotCapture a display, region, window, app, or the whole desktopclickClick at a global coordinate, with modifiers and multi-clickmove_mouseMove the pointer (hover states)dragPress, drag along an interpolated path, releasescrollScroll the wheel, optionally after moving the pointer- +7 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Remote Pc MCP
{
"mcpServers": {
"remote-pc-mcp": {
"command": "uvx",
"args": [
"remote-pc-mcp"
],
"env": {
"REMOTE_PC_MCP_TOKEN": "YOUR_REMOTE_PC_MCP_TOKEN_HERE"
}
}
}
}
Clickr
No confirmed install command for Clickr yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Remote Pc MCP is categorized under OS Automation and uses a local stdio subprocess. Clickr belongs to OS Automation and uses an install path we have not confirmed yet. Pick Remote Pc MCP for os automation work and Clickr for os automation.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Clickr has no confirmed install command yet — follow its own setup instructions.
Remote Pc MCP is listed as free. Auth: api key required. Clickr is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add remote-pc-mcp and tekmidian-clickr as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Remote Pc MCP has a quality signal of 55/100 (Good) with 0 views, 0 installs and 6 GitHub stars. Clickr has 49/100 (Fair) with 0 views, 0 installs and 1 GitHub stars.