A side-by-side look at the ScreenPilot and Glass MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
ScrollingScroll in different directions and to specific positions
Glass 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.
Glass
No confirmed install command for Glass 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. Glass belongs to OS Automation and uses an install path we have not confirmed yet. Pick ScreenPilot for os automation work and Glass 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. Glass 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 fixed-width-glass 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. Glass has 49/100 (Fair) with 2 views, 0 installs and 18 GitHub stars.