Skip to main content
Glama
kaannsaydamm

OmniCommanderMCP

by kaannsaydamm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to OmniCommanderMCP

No user-submitted related servers found.

    Related Servers

    • fleet

      xeniak123
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to remotely control multiple computers via MCP: run commands, manage files, install software, view and control screens, and execute parallel tasks across machines.
      132 npm
      MIT

    • devbox-mcp

      gurolg
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to execute shell commands, manage long-running processes, and read/write files on the host machine with the permissions of the user running the server.
      2 npm
      MIT

    • Codex Local Ops

      hattimon
      A
      license
      D
      quality
      B
      maintenance
      Enables controlled local developer operations including file and process management, shell execution, SSH, WSL, Docker, Git, browser and desktop automation, media processing, and asynchronous jobs through MCP.
      146
      MIT

    • win-rdp-mcp

      stubbedev
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables remote control of a Windows desktop via MCP, including screenshots, mouse and keyboard, window management, PowerShell, files, services, registry, scheduled tasks, event log, and network checks.
      14 npm
      MIT

    • Infinite_computer_use_mcp

      olter-tn
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP-capable AI assistants to control a Windows computer through GUI automation, file and process operations, PowerShell commands, durable background jobs, and binary file transfer with downloadable exports.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.1/5.0

    Scored across 27 tools

    Disambiguation4/5

    Most tools have distinct purposes, but capture_screen and capture_screen_image are very similar (different output format), and close_application and kill_process could be confused if descriptions aren't carefully read. Overall, the set is fairly well-disambiguated.

    Naming Consistency4/5

    The majority of tools follow a verb_noun pattern (e.g., capture_screen, clipboard_get), but system_info, network_info, windows_registry, and package_manager deviate. This minor inconsistency slightly lowers the score but the pattern is still recognizable.

    Tool Count4/5

    With 27 tools, the server covers a broad range of system operations. While slightly on the high side, the count is justified by the comprehensive scope (screen, clipboard, files, processes, system info, etc.). It's not excessive for the intended use case.

    Completeness4/5

    The tool set covers most essential system operations: file management, process control, clipboard, screen capture, system info, networking, services, and package management. Minor gaps (e.g., no mouse scroll, no file search) but overall quite complete for a system commander.

    Maintenance

    ActivityStale
    ResponsivenessUnresponsive

    Resources