Skip to main content
Glama
quantum-encoding

Terminal MCP Server

by quantum-encoding
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Terminal MCP Server

No user-submitted related servers found.

    Related Servers

    • Terminal MCP Server

      Mohamedmagdy21
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to create and interact with isolated tmux terminal sessions in real time, supporting command execution, output capture, and session management.
      -

    • Tmux MCP Server

      audibleblink
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to manage local tmux sessions, including creating and controlling sessions, windows, and panes, sending commands, and capturing terminal output.
      16
      6 npm
      Do What The F*ck You Want To Public

    • tmux-mcp

      WENLIXIAO-CS
      A
      license
      A
      quality
      C
      maintenance
      Allows AI assistants to create, manage, and interact with tmux sessions, windows, and panes programmatically.
      19
      MIT

    • Agent Collaboration MCP Server

      nishimoto265
      A
      license
      B
      quality
      D
      maintenance
      Enables AI agents to orchestrate a team of sub-agents through tmux sessions for complex task delegation and parallel implementation. It provides tools for launching agents, monitoring their real-time status, and managing communication between them.
      6
      7 npm
      26
      MIT

    • shell-use

      kyuheon-kr
      A
      license
      A
      quality
      D
      maintenance
      Enables agents to interact with CLI applications like vim, htop, and gdb by sending key inputs and capturing terminal output through tmux sessions.
      6
      MIT

    • ddx-term-mcp

      Dudoxx
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to execute commands in a shared tmux session that is simultaneously visible to a human via a web-based terminal UI.
      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/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool targets a distinct terminal operation: lifecycle (spawn/list/close), I/O (read/send/signal), and inspection (snapshot/resize/wait). Snapshot differs from list and read by combining an overview of all sessions with recent output. There is no real ambiguity between tools.

    Naming Consistency5/5

    All tool names follow a consistent terminal_verb pattern: spawn, list, read, send, send_signal, resize, snapshot, wait, close. Even the compound send_signal is clearly a verb_noun construction consistent with the rest. The naming is uniform and predictable.

    Tool Count5/5

    Nine tools is well-scoped for a terminal management server. Each tool covers a meaningful part of the terminal lifecycle without unnecessary redundancy. The count feels complete and not bloated.

    Completeness5/5

    The surface covers the full terminal workflow: spawn, interact, read, signal, resize, wait for output, snapshot, and close. There are no obvious missing operations that would prevent an agent from driving a terminal session effectively. The inclusion of permission-prompt handling in terminal_wait rounds out practical needs.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources