mcp server
Glasswarp
Eyes and hands on real Windows PCs — observe, click, type via Glasswarp API.
Description as published by the maintainer. Source
- version 0.1.0
- active
active — Most recent push to the repository was 2026-08-01.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| GitHub stars | 0 | Number of GitHub accounts that bookmarked this repository since it was created. It is a bookmark count, not installs, not active users and not quality. | cumulative, all time | GitHub | |
| Last commit | 2026-08-01 | Date of the most recent push to any branch. This is the strongest cheap indicator of whether the project is still maintained. | point in time | GitHub | |
| Open issues | 1 | Open issues plus open pull requests, as GitHub counts them together. A high number can mean an active project or an abandoned one. | as of fetch | GitHub | |
| Latest published version | 0.1.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-07-25 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| License | Apache-2.0 | Licence GitHub detected in the repository. Detection can be wrong; the LICENSE file is authoritative. | as of fetch | GitHub | |
| First listed in the MCP Registry | 2026-07-25 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| repository status | active | The repository exists on GitHub and is not archived. This says nothing about how recently it was worked on. | as of fetch | GitHub |
Where to get it
Related, by what their authors tagged them
-
io.github.antbotlab/mac-use-mcp
— last commit 2026-05-01, shares computer-use, desktop-automation
Zero-dependency macOS desktop automation for AI agents. 18 tools via MCP. macOS 13+.
-
GNOME UI MCP
— last commit 2026-08-02, shares desktop-automation
GNOME Wayland desktop automation via AT-SPI discovery and Mutter input.
-
io.github.developerz-ai/ui-debugger-mcp
— last commit 2026-08-08, shares desktop-automation
Autonomous UI debugging MCP server: an agent drives the browser/desktop, reports bugs + UX issues.
-
Claude KVM
— last commit 2026-07-06, shares computer-use
MCP server — control remote desktops via VNC with a native Swift daemon and Apple Vision OCR
-
io.github.bytedance/mcp-server-browser
— last commit 2026-08-05, shares computer-use
MCP server for browser use access
-
io.github.bytedance/mcp-server-commands
— last commit 2026-08-05, shares computer-use
An MCP server to run arbitrary commands
-
io.github.bytedance/mcp-server-filesystem
— last commit 2026-08-05, shares computer-use
MCP server for filesystem access
-
io.github.bytedance/mcp-server-search
— last commit 2026-08-05, shares computer-use
MCP server for web search operations
-
eliasoulkadi-shokunin-agent-browser
— last commit 2026-08-02, shares windows-automation
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, fi…
-
eliasoulkadi-shokunin-agent-tools
— last commit 2026-08-02, shares windows-automation
Run 150+ AI apps via inference.sh CLI - image generation, video creation, LLMs, search, 3D, Twitter automation. Models:…
These share tags the maintainers applied themselves, such as computer-use, desktop-automation, windows-automation. Common tags like "mcp" or "ai" are ignored for this: agreeing with six hundred other projects is not a similarity.
This is not a recommendation and not a test result. It is a map of what the authors said their work is about.
How the author describes it
Topics the maintainer set on GitHub: ai-agents, computer-use, desktop-automation, mcp, windows-automation.
Bring your own setup
We take apart real AI setups every week and show what broke, what cost too much, and what the trace actually said. If you run agents on real work, that is where the useful conversation is.
Join ZBS AI Practice Lab