How Persistence Works vs ScreenPilot
A side-by-side look at the How Persistence Works and ScreenPilot MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose How Persistence Works for os automation work over a hosted endpoint; choose ScreenPilot for os automation. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose How Persistence Works when
- You need dedicated capabilities in the OS Automation domain.
- You prefer a remote HTTP/SSE transport.
Choose ScreenPilot when
- You need dedicated capabilities in the OS Automation domain.
- You want tools like
Scrolling.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | OS Automation | OS Automation |
| Quality signal | 29/100 · Emerging | 47/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Remote HTTP/SSE | — |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 6 | 55 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 1 |
| Full listing | View How Persistence Works | View ScreenPilot |
Tools & capabilities
How Persistence Works tools
No tool names declared yet. Check the project README from the listing page.
ScreenPilot tools 1
ScrollingScroll in different directions and to specific positions
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.
How Persistence Works
{
"mcpServers": {
"bridge-mcp": {
"url": "https://your-project.fastmcp.app/mcp"
}
}
}
ScreenPilot
No confirmed install command for ScreenPilot yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
How Persistence Works is categorized under OS Automation and uses a remote HTTP/SSE transport. ScreenPilot belongs to OS Automation and uses an install path we have not confirmed yet. Pick How Persistence Works for os automation work and ScreenPilot 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. ScreenPilot has no confirmed install command yet — follow its own setup instructions.
How Persistence Works has no declared pricing — check the project's own site. ScreenPilot 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 bridge-mcp and mtehabsim-screenpilot as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, How Persistence Works has a quality signal of 29/100 (Emerging) with 1 views, 0 installs and 6 GitHub stars. ScreenPilot has 47/100 (Fair) with 1 views, 0 installs and 55 GitHub stars.