Skip to main content
Glama
Sign In
Heming9

Agenterm

by Heming9
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Remote

Related Servers

Alternatives to Agenterm

No user-submitted related servers found.

    Related Servers

    • interminal

      QiuwenZheng
      A
      license
      A
      quality
      B
      maintenance
      MCP server for SSH and local terminal access. Supports interactive commands, long-running processes, and TUI apps like tmux/zellij
      6
      4
      MIT

    • Codex SSH Terminal MCP

      NullPointerChef
      A
      license
      B
      quality
      D
      maintenance
      Agent-native SSH control plane with a local Web Terminal, human-in-the-loop secret input, keychain-backed profiles, and user-confirmed uploads for Codex, Claude Code, and MCP-compatible coding agents.
      18
      1
      Apache 2.0
    • AgentVPS by agentsdance

      AgentVPSofficial

      agentsdance
      A
      license
      Not graded
      quality
      A
      maintenance
      Turns your own VPS into an agent's remote computer, exposing shell and code execution, persistent workspace files, Bash PTYs, a Chromium browser, notes, scheduled tasks, and a streamed Linux desktop over MCP. Clients such as Claude Code or Codex can also use an authenticated REST API, CLI, and web console to drive the same shared workspace.
      27 npm
      22
      MIT

    • CommandCore

      bazobehram
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI/MCP clients to enumerate, select, and operate authorized remote computers through one OAuth-protected, self-hosted endpoint, with devices connecting outbound and keeping their own cryptographic identities. It layers OAuth scopes, account-to-device grants, server profiles, and device-local ceilings to govern filesystem, shell, process, transfer, Git, and signed agent lifecycle operations with auditable results.
      AGPL 3.0
    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.5/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct part of the remote-terminal workflow: client onboarding, device listing, non-interactive command execution, and session start/read/write/stop. The only possible overlap is execute_command versus session_start, but the descriptions clearly separate short non-interactive commands from interactive long-running sessions.

    Naming Consistency4/5

    The session tools consistently use resource-prefixed action names (session_start, session_read, session_write, session_stop), while client and command tools use verb_noun names (create_client, list_clients, execute_command). This is readable and predictable overall, but the mixed prefix convention keeps it from being perfectly uniform.

    Tool Count5/5

    Seven tools is well-scoped for a remote terminal/device management server. The set covers client setup, device discovery, command execution, and the full interactive session lifecycle without redundant tools.

    Completeness4/5

    Core workflows are covered: creating invitations, waiting for devices, executing commands, and managing interactive sessions. Minor lifecycle gaps remain, such as revoking client tokens or listing existing sessions, but agents can largely work around these.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources