Skip to main content
Glama
hungtranbkit

Terminal MCP

by hungtranbkit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Terminal MCP

No user-submitted related servers found.

    Related Servers

    • tmux-mcp

      trolleydodger1988
      F
      license
      A
      quality
      D
      maintenance
      A persistent, stateful MCP server that exposes a detached tmux session to clients, enabling shell command execution, terminal buffer reading, and control signal sending via JSON-RPC over stdio.
      3
      -

    • agent-runtime-mcp

      liqiangcc
      F
      license
      A
      quality
      A
      maintenance
      Enables MCP-based communication with existing interactive terminal channels, such as shells or agent CLIs, by listing, reading, writing text, and sending control signals to tmux sessions without creating or managing them.
      7
      -

    • Secure Host MCP

      Razewang
      A
      license
      Not graded
      quality
      A
      maintenance
      Exposes a Windows or Linux host terminal to remote MCP clients via Streamable HTTP, enabling command execution, tunnel management, and privileged operations with security features like OAuth and audit logging.
      33 npm
      2
      MIT

    • interminal

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

    • safe-mcp-bridge-v2

      efe-arv
      A
      license
      Not graded
      quality
      C
      maintenance
      A fail-closed policy boundary that translates local stdio MCP clients to authenticated Streamable HTTP servers, enforcing allowlists or read-only modes and redacting credentials from audit trails.
      Apache 2.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

    B3.2/5.0

    Scored across 13 tools

    Disambiguation4/5

    Tools are mostly distinct, with a clear split between direct session operations and logical binding operations. The only mild ambiguity is between terminal_tail and terminal_capture, but their descriptions differentiate recent output from larger scrollback.

    Naming Consistency4/5

    All tools share a terminal_ prefix and use snake_case, with a consistent _bound suffix for binding-resolved variants. Minor inconsistencies exist, such as get_binding vs list_bindings and send_bound omitting the _text qualifier used by send_text, but the overall pattern is predictable.

    Tool Count5/5

    Thirteen tools is well-scoped for a terminal/tmux MCP server. The surface is organized into two coherent families—session inspection/control and persistent bindings—without obvious redundancy or bloat.

    Completeness4/5

    The set covers core listing, reading, status, input, and binding lifecycle operations. There are minor gaps such as no bound capture variant and no explicit binding update, but most expected workflows for a restricted terminal interface are supported.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources