Skip to main content
Glama
AICommander-dev

AI Commander

by AICommander-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

Related Servers

Alternatives to AI Commander

No user-submitted related servers found.

    Related Servers

    • 2ools MCP Server by 2ools

      2ools MCP Serverofficial

      2ools
      A
      license
      A
      quality
      A
      maintenance
      Remote MCP server for 2ools—build, version, review, and export websites, web apps, and games from the AI chat you already use. This repository includes a credential-free stdio proxy and Dockerfile that forward introspection to the verified remote endpoint without mocking tools.
      43
      1
      MIT

    • onputer

      tteggu87
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI chat clients to securely access and manage local files, run terminal commands, work with Git repositories, and read AGENTS.md instructions and skills via a stateless Streamable HTTP MCP server.
      MIT

    • CodePier

      cyeinfpro
      A
      license
      Not graded
      quality
      A
      maintenance
      Connects ChatGPT and MCP clients to authorized local development environments, enabling secure file access, shell execution, persistent tasks, browser/desktop control, and remote management of projects.
      12
      MIT

    • Universal Host Manager MCP

      Abktya
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients such as ChatGPT and Claude to administer Linux or macOS hosts through authenticated Streamable HTTP, including running shell commands, reading and writing files within a workspace, listing directories, and retrieving system metrics.
      118 PyPI
      1
      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

    A4.4/5.0

    Scored across 11 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes: job lifecycle tools, file transfer, screenshot, status, and list. The main overlap is between remote_exec and remote_job_start, but their descriptions strongly differentiate short-lived vs. detached long-running work, so an agent should rarely misselect.

    Naming Consistency4/5

    The remote_job_* family is perfectly consistent, and remote_pull/remote_push/remote_exec/remote_screenshot follow a clear remote_ prefix pattern. The exceptions are session_status and list_machines, which break the prefix convention but are still readable and predictable.

    Tool Count5/5

    11 tools is well-scoped for a remote machine management server. Each tool covers a distinct operation: shell execution, job lifecycle, file transfer, screenshots, and machine discovery/status, with no obvious redundancy or bloat.

    Completeness4/5

    The job lifecycle is complete (start, list, status, logs, cancel), and file transfer covers both directions. Minor gaps exist, such as no remote filesystem browsing or direct machine management beyond status checks, but these are workaroundable via remote_exec and are not core dead ends.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources