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