Baepsae vs Clickr
A side-by-side look at the Baepsae 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 Baepsae 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 Baepsae when
- You need dedicated capabilities in the OS Automation domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
BAEPSAE_NATIVE_PATH. - You want tools like
baepsae_help, baepsae_version, doctor.
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 | 59/100 · Good | 49/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | BAEPSAE_NATIVE_PATH | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 26 | 1 |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 47 | 19 |
| Full listing | View Baepsae | View Clickr |
Tools & capabilities
Baepsae tools 47
baepsae_helpShow help. Optionally pass subcommand name for compatibility reference.baepsae_versionShow server and native binary versions.doctorRun readiness self-checks for host process, parent process, native binary, booted simulator availability, and accessibility permission.list_appsList running macOS applications with their bundle IDs.get_focused_appGet information about the currently focused macOS app.list_simulatorsList available simulators using simctl.open_urlOpen a URL in the simulator (e.g. Safari or deep link).install_appInstall an app (.app, .ipa) on the simulator.uninstall_appUninstall an app from the simulator.launch_appLaunch an installed app on the simulator.terminate_appTerminate a running app on the simulator.analyze_uiDescribe app UI hierarchy. Works with both simulator (udid) and macOS (bundleId/appName) targets.- +35 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.
Baepsae
{
"mcpServers": {
"baepsae": {
"command": "npx",
"args": [
"-y",
"mcp-baepsae@latest"
],
"env": {
"BAEPSAE_NATIVE_PATH": "YOUR_BAEPSAE_NATIVE_PATH_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
Baepsae 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 Baepsae 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.
Baepsae has no declared pricing — check the project's own site. 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 baepsae and tekmidian-clickr as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Baepsae has a quality signal of 59/100 (Good) with 2 views, 0 installs and 26 GitHub stars. Clickr has 49/100 (Fair) with 0 views, 0 installs and 1 GitHub stars.