A side-by-side look at the Glass and ScreenPilot MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
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.
Glass
No confirmed install command for Glass yet — follow the setup steps linked from its listing page rather than a guessed package name.
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
Glass is categorized under OS Automation and uses an install path we have not confirmed yet. ScreenPilot belongs to OS Automation and uses an install path we have not confirmed yet. Pick Glass for os automation work and ScreenPilot 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.
Glass is listed as free. Auth: no auth required. 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 fixed-width-glass and mtehabsim-screenpilot as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Glass has a quality signal of 49/100 (Fair) with 2 views, 0 installs and 18 GitHub stars. ScreenPilot has 47/100 (Fair) with 1 views, 0 installs and 55 GitHub stars.