Skip to main content
Glama
SammySnake-d

proc-repl-mcp

by SammySnake-d
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to proc-repl-mcp

No user-submitted related servers found.

    Related Servers

    • Tmux MCP Server

      MediocreTriumph
      A
      license
      A
      quality
      D
      maintenance
      Enables programmatic control over tmux terminal sessions for SSH access, command execution, and terminal automation. Supports creating sessions, sending commands, capturing output, and managing multiple panes for interactive debugging and monitoring.
      8
      8 npm
      MIT

    • portal

      tiefeiyu
      A
      license
      A
      quality
      A
      maintenance
      Enables interaction with long-running interactive programs such as SSH, GDB, and REPLs. Provides tools to start, monitor, control, read/write I/O for these processes.
      13
      1
      MIT

    • Menager MCP Server

      1999AZZAR
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents or human operators to spawn, monitor, drive, and hook into child terminal sessions—such as CLI tools, interactive shells, and polyglot runtimes—via POSIX pseudo-terminals, providing multiplexed control, event interception, and memory-bounded observability for orchestration.
      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
    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

    The tools are clearly split into regular subprocess sessions and tmux sessions, each with distinct lifecycles and the tmux_ prefix clearly marking the latter. However, send/read/run could be confused with tmux_send_keys/tmux_capture_pane/tmux_step if descriptions are not carefully read, so a small amount of ambiguity remains.

    Naming Consistency3/5

    Regular session tools mix verb_noun patterns (open_session, close_session) with bare verbs (send, read, run). Tmux tools are consistently prefixed with tmux_ but include both verb_noun (tmux_send_keys) and bare verb (tmux_step) forms. The mixed conventions are readable but not fully consistent.

    Tool Count5/5

    13 tools is well within the ideal range and appropriate for managing two types of interactive sessions (PTY and tmux). Each tool serves a distinct purpose in the workflow, and none feel redundant or excessive.

    Completeness5/5

    The tool set provides full lifecycle coverage for both regular and tmux sessions: open, list, send/read, and close, plus useful conveniences like run, step, capture, and resize. There are no obvious dead ends or missing core operations for interacting with external processes.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources