A
licenseNot graded
qualityB
maintenanceRemote-first, model-independent Windows execution MCP for ChatGPT, Claude, Gemini, and other MCP-compatible AI clients.
MIT
codex-hermes-worker
by RANJIANG23
Related Servers
Alternatives to codex-hermes-worker
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceA Windows-native MCP gateway that lets any MCP-capable host orchestrate local coding-agent CLIs as external workers.11Apache 2.0
- AlicenseNot gradedqualityCmaintenanceWindows 11 local MCP bridge enabling authorized access to development workspaces, command execution, and UAC-gated admin operations for ChatGPT-like clients.2 npm8MIT
- AlicenseNot gradedqualityAmaintenanceEnables 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.2 npmMIT
- AlicenseNot gradedqualityBmaintenanceProvides a Windows-first local AI-agent gateway with configurable tools for files, Git, processes, Windows automation, WSL, browser control, durable agent runs, memory, verification, and intelligent routing, while exposing a secure MCP endpoint for ChatGPT Web and a local web UI.6 npmMIT
- AlicenseNot gradedqualityBmaintenanceProvides a local Windows control plane for PowerShell and AI CLIs, exposing MCP tools for safe terminal sessions, bounded provider calls, routing, committees, and run receipts.5 npmMIT
TDQS
A3.5/5.0
Scored across 9 tools
Disambiguation5/5
Each tool maps to a clearly distinct operation: listing, reading text, reading binary, extracting strings, metadata, filename search, content search, ffprobe, and function-record query. Potential overlaps like list_workspace_files vs get_file_metadata are separated by scope (directory-level vs file-level detail).
Naming Consistency5/5
All tool names follow a consistent snake_case verb-first pattern such as list_, read_, get_, extract_, search_, run_, and query_. The object is always the target resource, and there are no mixed conventions or vague verbs.
Tool Count5/5
Nine tools is a well-scoped size for a read-only file/workspace inspection server. Each tool provides a distinct capability without redundancy, and the count is neither bloated nor too thin.
Completeness4/5
The read-only surface is broadly complete: listing, text and binary reads, metadata, strings, filename/content search, media probing, and function-record lookup are all covered. The main minor gap is the lack of a binary-content search, though bounded slices and string extraction provide workarounds.
Maintenance
ActivityStale
ResponsivenessNo issues