Skip to main content
Glama
Quinnverse

MCP Terminal Controller

by Quinnverse
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to MCP Terminal Controller

No user-submitted related servers found.

    Related Servers

    • devbox-mcp

      gurolg
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to execute shell commands, manage long-running processes, and read/write files on the host machine with the permissions of the user running the server.
      0
      MIT

    • pokeclaw

      madebydia
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables MCP clients to spawn and control Codex CLI and Claude Code sessions on the host machine, with session management and filesystem access.
      4
      MIT

    • muster

      BrutalSystems
      A
      license
      B
      quality
      B
      maintenance
      Enables launching and supervising local Codex and Claude Code agent sessions and one-shot tasks, exposing run, list, stop, and output operations over MCP with session-scoped permissions and sandbox controls.
      2
      3,029 npm
      1
      MIT

    • runkeep-mcp

      3xjn
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables management of long-running development processes (such as dev servers, compilers, and watchers) from MCP hosts. Provides tools to start, stop, restart, check status, view logs, and send input to managed processes.
      MIT

    • shell-session-mcp

      CarefulDeveloper
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides persistent interactive shell sessions via pseudo-terminals for MCP agents, enabling bidirectional communication, incremental reads, and stateful command execution across steps.
      5 npm
      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 5 tools

    Disambiguation5/5

    Each tool maps to a distinct lifecycle stage: start, write, read, status, terminate. The only near-overlap is status reporting 'output availability' versus read returning output, but the descriptions make clear status is metadata-only while read consumes records from a cursor.

    Naming Consistency5/5

    All five tools share a uniform terminal_ prefix with a single-word verb suffix (start, write, read, status, terminate). Fully predictable and consistent.

    Tool Count5/5

    Five tools is exactly the minimal complete set for process session control, with no redundant operations. Each tool earns its place in the lifecycle.

    Completeness4/5

    Start/write/read/status/terminate covers the full session lifecycle including graceful and forced termination. Minor gaps exist for interactive/pty use: no terminal_resize and no dedicated signal-send tool (Ctrl-C must be emulated via write), and no session listing, but agents can work around these.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources