Skip to main content
Glama
UserB1ank

interactive-process-mcp

by UserB1ank
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Local

Related Servers

Alternatives to interactive-process-mcp

No user-submitted related servers found.

    Related Servers

    • MCP Shell Server

      mako10k
      A
      license
      B
      quality
      A
      maintenance
      A secure MCP server for shell operations, terminal management, and process control, enabling AI assistants to safely execute commands and manage interactive sessions.
      13
      161 npm
      6
      MIT

    • mcp-ssh-interactive

      qnxqnxqnx
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that enables AI agents to run fully interactive SSH sessions (via tmux) and execute commands like a human operator, with persistent sessions and multiple concurrent connections.
      6
      MIT

    • terminal-bridge-mcp

      dividduang
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that bridges AI assistants to real terminal sessions, enabling creation, management, and interaction with persistent PTY processes for running commands, monitoring output, and debugging.
      1
      MIT

    • termcp

      open-mcp-ai
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to interact with real terminal sessions across local and remote hosts, driving multi-turn interactive programs like TUIs, REPLs, and SSH prompts through MCP.
      32
      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

    A3.7/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool has a distinct and clear purpose: starting, listing, inspecting, sending input, reading output, resizing, and terminating sessions. No overlap or ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case, such as start_process, read_output, and terminate_process. The naming is predictable and uniform.

    Tool Count5/5

    With 8 tools, the set is well-scoped for managing interactive processes. It covers essential operations without being overwhelming or sparse.

    Completeness4/5

    The tool surface covers core lifecycle operations (start, interact, read, resize, terminate). Minor gaps exist, such as explicit process status checking, but overall it is comprehensive.

    Maintenance

    ActivityInactive
    ResponsivenessResponsive

    Resources