Skip to main content
Glama
rnd-pro
by rnd-pro

Related Servers

Alternatives to terminal-x-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server enabling AI agents to interact with terminal applications through structured Terminal State Tree representation. Works with any AI assistant that supports the Model Context Protocol.
      53 npm
      19
      MIT
    • A
      license
      C
      quality
      C
      maintenance
      A server that enables AI assistants to execute terminal commands and retrieve outputs via the Model Context Protocol (MCP).
      3
      27
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Terminal MCP server for AI coding agents with persistent PTY sessions, ring-buffer incremental reads, headless xterm screen capture, multi-agent orchestration, and a real-time web dashboard.
      22 npm
      23
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      A command-line interface and MCP server for managing and monitoring multiple development services through a unified terminal UI. It enables users to interact with service logs, filter messages, and control development environments directly via Model Context Protocol integration.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Multi-threaded terminal management MCP server for AI assistants, enabling async command execution, batch operations, and real-time web monitoring with up to 100 concurrent terminals.
      2
      MIT

    TDQS

    B3.4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: execute_command runs commands, monitor_processes observes processes, validate_security assesses command risk without executing, and plan_workflow designs multi-step sequences. The slight overlap between execute_command's built-in validation and validate_security is separated by execution vs assessment, so no real ambiguity exists.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern: execute_command, monitor_processes, validate_security, plan_workflow. The verbs and nouns are clear and uniformly formatted, making the tool names predictable and easy to understand.

    Tool Count5/5

    With 4 tools, the server is well-scoped for its stated purpose of secure terminal interaction. Each tool covers a distinct phase (planning, validation, execution, monitoring) without redundancy or bloat, falling comfortably within the ideal 3-15 range.

    Completeness3/5

    The set covers core terminal operations but has notable gaps: no tool for process control (e.g., kill, stop), and plan_workflow only creates a plan without an execution mechanism to run the whole workflow at once. While execute_command can handle many actions, these missing operations limit the server's end-to-end workflow support.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues