Screenhand vs How Persistence Works
A side-by-side look at the Screenhand and How Persistence Works MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
S
ScreenhandOS Automation · Local subprocess (stdio)Give AI eyes and hands on your desktop. ScreenHand is an open-source MCP server that lets Claude and other AI agents see your screen, click buttons, type text, and control any app on macOS and Windows.52GoodAuth: no auth requiredVerdict: choose Screenhand for os automation work as a local process; choose How Persistence Works for os automation. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
SChoose Screenhand when
- You need dedicated capabilities in the OS Automation domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Choose How Persistence Works when
- You need dedicated capabilities in the OS Automation domain.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | S Screenhand | |
|---|---|---|
| Category | OS Automation | OS Automation |
| Quality signal | 52/100 · Good | 23/100 · Emerging |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 15 | 6 |
| Directory activity | 1 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Screenhand | View How Persistence Works |
Tools & capabilities
Screenhand tools
No tool names declared yet. Check the project README from the listing page.
How Persistence Works tools
No tool names declared yet. Check the project README from 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.
Screenhand
{
"mcpServers": {
"screenhand": {
"command": "npx",
"args": [
"-y",
"screenhand"
]
}
}
}
How Persistence Works
No confirmed install command for How Persistence Works yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Screenhand is categorized under OS Automation and uses a local stdio subprocess. How Persistence Works belongs to OS Automation and uses an install path we have not confirmed yet. Pick Screenhand for os automation work and How Persistence Works 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. How Persistence Works has no confirmed install command yet — follow its own setup instructions.
Screenhand is listed as free. Auth: no auth required. How Persistence Works has no declared pricing — check the project's own site. 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 screenhand and bridge-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Screenhand has a quality signal of 52/100 (Good) with 1 views, 0 installs and 15 GitHub stars. How Persistence Works has 23/100 (Emerging) with 2 views, 0 installs and 6 GitHub stars.