Agentfenster vs Screen Control
A side-by-side look at the Agentfenster and Screen Control MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Agentfenster for os automation work over a hosted endpoint; choose Screen Control 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 Agentfenster when
- You need dedicated capabilities in the OS Automation domain.
- You prefer a remote HTTP/SSE transport.
Choose Screen Control 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 | 37/100 · Fair | 41/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | 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 | 0 | 4 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Agentfenster | View Screen Control |
Tools & capabilities
Agentfenster tools
No tool names declared yet. Check the project README from the listing page.
Screen Control 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.
Agentfenster
{
"mcpServers": {
"agentfenster": {
"url": "https://agentfenster.com/mcp"
}
}
}
Screen Control
{
"mcpServers": {
"screen-control": {
"url": "http://127.0.0.1:8751/mcp"
}
}
}
Frequently asked questions
Agentfenster is categorized under OS Automation and uses a remote HTTP/SSE transport. Screen Control belongs to OS Automation and uses a remote HTTP/SSE transport. Pick Agentfenster for os automation work and Screen Control 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.
Agentfenster has no declared pricing — check the project's own site. Screen Control 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 agentfenster and screen-control as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Agentfenster has a quality signal of 37/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Screen Control has 41/100 (Fair) with 1 views, 0 installs and 4 GitHub stars.