Skip to main content
Glama
MatheusAlves96

termix-mcp

by MatheusAlves96
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

Related Servers

Alternatives to termix-mcp

No user-submitted related servers found.

    Related Servers

    • termux-mcp

      timerloggedout-spec
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables LLM agents to remotely perform Termux/Android operations through a hosted MCP endpoint, including device status checks, shell command execution, and package management.
      11 npm
      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.
      1
      MIT

    • mcp-ssh-interactive

      qnxqnxqnx
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that enables AI agents to run fully interactive SSH sessions (via tmux) and execute commands like a human operator, with persistent sessions and multiple concurrent connections.
      6
      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

    C2.1/5.0

    Scored across 184 tools

    Disambiguation2/5

    Many tools have overlapping or duplicate responsibilities, such as termix_hosts_get_command_history vs termix_terminal_history_get_command_history, and multiple SSH session establishment/authentication flows across docker, files, and metrics. The repeated TOTP/Warpgate completion tools and similar 'get stats' tools across Proxmox and metrics further blur boundaries, making it easy for an agent to select the wrong tool.

    Naming Consistency2/5

    The general termix_<domain>_<action>_<object> pattern is present but inconsistently applied: actions mix get/list/read/fetch/check, some names repeat the domain twice like termix_proxmox_get_cached_proxmox_node_stats_host and termix_fleets_add_host_fleets_static_membership, and phrasing varies widely from 'get_all_ssh_hosts' to 'create_temporary_ssh_connection_without_saving'. The naming is readable in isolation but does not form a predictable, uniform convention.

    Tool Count1/5

    184 tools is an extreme count for an MCP server, far beyond the 3-15 well-scoped range and even beyond the 16-25 'heavy' range. While Termix is a broad platform covering many domains, exposing this many tools as one flat MCP surface creates severe selection overhead and coherence problems.

    Completeness2/5

    The server covers many feature areas—hosts, credentials, snippets, fleets, metrics, docker, files, tunnels, automations, alerts, audit logs, and more—but there are notable CRUD gaps: no delete operations for hosts, credentials, snippets, fleets, or automations are present. The surface is broad but incomplete for standard lifecycle management, which will force agents into dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources