Skip to main content
Glama
KevinBuettner

docent-terminal-mcp

by KevinBuettner
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to docent-terminal-mcp

No user-submitted related servers found.

    Related Servers

    • ddx-term-mcp

      Dudoxx
      A
      license
      Not graded
      quality
      D
      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

    • Persistent Shell MCP

      TNTisdial
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to execute shell commands and manage long-running processes within persistent tmux sessions across isolated workspaces. It features a dual-window architecture to separate raw command execution from interactive terminal output.
      8
      9 npm
      1
      MIT

    • termmirror

      Ar9av
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to drive real interactive terminal sessions—PTYs, TUIs, REPLs, SSH, even another agent's CLI—with a live web view where humans can watch and type in.
      5 npm
      2
      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

    • 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.
      -
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A4.1/5.0

    Scored across 15 tools

    Disambiguation4/5

    Each tool has a distinct role: session lifecycle tools (session_create, session_split, session_list, session_resize, session_close, session_logs) are clearly separated, and interactive tools (run, send, wait, expect) are differentiated by whether they wait for completion, type keystrokes, or script prompts. Minor conceptual overlap between run/send/wait exists, but the detailed descriptions resolve it.

    Naming Consistency4/5

    All tools use lower_snake_case, and session management tools share a consistent session_ prefix (session_create, session_split, session_list, etc.). However, non-session tools are a mix of plain verbs (run, send, wait, read, search, expect) and noun_verb (shell_integrate), and 'regions' is a bare noun, so the pattern is not uniformly verb_noun.

    Tool Count5/5

    15 tools map cleanly to the domain's needs: 6 session lifecycle operations, 5 interaction tools, 3 output inspection tools, plus a guide. Each tool earns its place and no tool appears redundant or trivial for terminal session management.

    Completeness5/5

    The surface covers the full terminal session lifecycle: creating, splitting, listing, resizing, closing, and retaining logs, plus rich interaction (run, send, expect, wait, shell_integrate) and output analysis (read, search, regions). No obvious gaps for the stated purpose of managing and interacting with terminal sessions.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources