Skip to main content
Glama

Related Servers

Alternatives to codex-hermes-worker

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Windows 11 local MCP bridge enabling authorized access to development workspaces, command execution, and UAC-gated admin operations for ChatGPT-like clients.
      2 npm
      8
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables 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.
      1 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Self-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
    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides 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.
      5 npm
      MIT

    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

    ActivityInactive
    ResponsivenessNo issues