windows-terminal
Related Servers
Alternatives to windows-terminal
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables MCP-speaking clients to control a real desktop via the computer_use tool, including clicking, typing, scrolling, dragging, key combos, app focus, and screen/accessibility capture. It also provides a verdict system that verifies whether input actions had their intended effect, with configurable approval modes.1MIT
- AlicenseNot gradedqualityAmaintenanceGives AI agents full control of a Windows computer over MCP through 63 native tools — screenshots and UI trees for vision, mouse/keyboard input, Chrome control via CDP, plus files, terminal, processes, and SSH/SFTP. The agent can look at the screen, click, type, launch apps, run commands, and verify each step with a fresh screenshot.47MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to capture multi-monitor screenshots with coordinate grids and perform mouse, keyboard, scrolling, dragging, and window-management actions on Windows via MCP tools or CLI. It provides pixel-accurate desktop automation for computer-use agents.MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP-capable agents to take desktop screenshots, click, scroll, and control an independent overlay pointer on Windows without taking over the real mouse. Supports background window-message input, observation-based verification, and lifecycle controls for safe desktop interaction.Apache 2.0
- AlicenseBqualityBmaintenanceNido is a local QEMU VM manager. Install it on your computer from https://github.com/Josepavese/nido and run nido mcp via stdio, or use npx -y nido-mcp@latest mcp with QEMU installed locally. It manages VMs on that same computer; a server hosted by Glama cannot access your local VM inventory.62MIT
- AlicenseNot gradedqualityDmaintenanceA framework-agnostic computer-use MCP server that exposes core desktop operations (screen capture, mouse, keyboard, and file access) as standard MCP tools, enabling any MCP-compatible agent to drive a computer.1,698 npmMIT
TDQS
Scored across 9 tools
Each tool targets a clearly distinct action: viewing (screenshot), pointer input (click, move, scroll), keyboard input (type, key), lifecycle (start, stop), and observation (status). There is no meaningful overlap; click vs. move vs. scroll are cleanly separated by intent and description.
The set follows a consistent single-word imperative style (click, move, type, key, scroll, start, stop) with only two noun-like names (screenshot, status). This is a minor deviation and remains highly predictable.
Nine tools is well-scoped for controlling a Windows VM, and each tool earns its place across input, observation, and lifecycle control. There are no redundant or trivial tools.
The surface covers the core lifecycle (start/stop/status), screen observation, and essential input methods. Minor gaps exist, such as drag/double-click support and clipboard-based paste, but agents can work around them with available primitives.