ZeroIDE MCP
Related Servers
Alternatives to ZeroIDE MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceSelf-hosted server that lets ChatGPT, Grok, and stdio MCP clients read and write files, run PowerShell/CMD and interactive processes, and drive the Windows desktop through screenshots, window info, clicks, drags, and keyboard input. It connects via OpenAI Secure MCP Tunnels, an OAuth authorization-code + S256 PKCE HTTPS endpoint, or local stdio, exposing 38 tools under the user's own Windows account.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI clients to securely control and interact with a local Windows machine through 218 configurable tools for files, Git, processes, Windows UI, browser automation, WSL, Office, recovery, skills, and child MCP servers.11 npmMIT
- FlicenseNot gradedqualityCmaintenanceA local MCP server that enables AI agents to inspect and control a Windows machine through permission-gated tools for system information, windows, UI elements, files, applications, screenshots, input, and multi-step workflows.-
- FlicenseNot gradedqualityDmaintenanceA lightweight MCP HTTP server giving AI assistants real tools to interact with your Windows machine, including running commands, file access, system info, web search, and browser automation.1-
- FlicenseNot gradedqualityDmaintenanceA local, dependency-free MCP server that gives AI agents controlled access to the active Windows desktop, enabling automated interaction with applications through screenshots, clicks, typing, and window management.1-
- AlicenseBqualityDmaintenanceHigh-performance MCP server giving AI agents advanced filesystem and automation capabilities on Windows, with 26 tools across file I/O, search, Git, process management, and more.262MIT
TDQS
Scored across 19 tools
Each tool targets a distinct resource+action: file ops (read/write/edit/list/search/ops), command execution (run_command/job_status/job_output), and observability (audit_log/journal_entry/journal_log) are cleanly separated. The only soft overlap is in the 'communicate with the human/agents' cluster — user_message vs task_status both render in the tray, and agent_message vs await_owner both concern messaging — but the descriptions make the boundaries clear.
Everything is uniformly snake_case with no camelCase or casing drift, which is a strong baseline. However the style mixes verb_first action names (run_command, read_file, take_screenshot, list_directory) with noun_phrase resource names (task_status, agent_message, job_status, system_info, audit_log), so it misses a single predictable verb_noun pattern.
19 tools is at the upper edge of the ideal range but each group earns its place: file CRUD, shell exec + background job management, human/agent messaging, and audit/journal observability. Nothing looks redundant or filler, though it is on the heavier side of well-scoped.
Coverage is unusually thorough for an agent control plane: full file lifecycle (read/write/edit/delete/list/search/image), command execution with background jobs and paged output, owner and agent messaging, and audit+journal history. Minor gaps remain (no dedicated job-cancel/kill tool — it is only reachable via agent_message stopCommand — and no first-class git operations), but agents can work around these.