Omniparser Autogui MCP vs Agentfenster
A side-by-side look at the Omniparser Autogui MCP and Agentfenster MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Omniparser Autogui MCP for os automation work; choose Agentfenster for os automation over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Omniparser Autogui MCP when
- You need dedicated capabilities in the OS Automation domain.
- Its auth model fits you: No auth required.
Choose Agentfenster when
- You need dedicated capabilities in the OS Automation domain.
- You prefer a remote HTTP/SSE transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | OS Automation | OS Automation |
| Quality signal | 32/100 · Emerging | 37/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Remote HTTP/SSE |
| 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 | 72 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Omniparser Autogui MCP | View Agentfenster |
Tools & capabilities
Omniparser Autogui MCP tools
No tool names declared yet. Check the project README from the listing page.
Agentfenster 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.
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.
Agentfenster
{
"mcpServers": {
"agentfenster": {
"url": "https://agentfenster.com/mcp"
}
}
}
Frequently asked questions
Omniparser Autogui MCP is categorized under OS Automation and uses an install path we have not confirmed yet. Agentfenster belongs to OS Automation and uses a remote HTTP/SSE transport. Pick Omniparser Autogui MCP for os automation work and Agentfenster 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. Omniparser Autogui MCP has no confirmed install command yet — follow its own setup instructions.
Omniparser Autogui MCP is listed as free. Auth: no auth required. Agentfenster 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 non906-omniparser-autogui-mcp and agentfenster as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Omniparser Autogui MCP has a quality signal of 32/100 (Emerging) with 1 views, 0 installs and 72 GitHub stars. Agentfenster has 37/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.