Skip to main content
Glama
weyou

termio-mcp

by weyou
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to termio-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-terminal-bridge

      SHTO88
      F
      license
      Not graded
      quality
      B
      maintenance
      Provides AI agents with persistent, interactive pseudo-terminal sessions for running CLI tools, SSH, and AWS SSM, including support for prompts, concurrent commands, and a live web TUI.
      -

    • Menager MCP Server

      1999AZZAR
      A
      license
      Not graded
      quality
      B
      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

    • pty-mcp

      brkhrdt
      F
      license
      A
      quality
      C
      maintenance
      Enables AI agents to start and manage pseudo-terminal sessions, run shell commands and interact with REPLs programmatically.
      7
      -

    • Interactive Shell MCP

      lightos
      A
      license
      Not graded
      quality
      F
      maintenance
      Enables LLMs to create and manage persistent, interactive shell sessions with full terminal emulation and PTY support. It allows for sequential command execution and supports interactive programs like vim or htop through specialized streaming and snapshot output modes.
      5
      MIT

    • terminal-mcp

      mkpvishnu
      A
      license
      A
      quality
      A
      maintenance
      Give AI agents a persistent, interactive terminal with support for SSH, REPLs, database CLIs, TUI apps, and long-running processes.
      9
      29 PyPI
      11
      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.5/5.0

    Scored across 12 tools

    Disambiguation3/5

    Several tools have overlapping purposes: exec_expect and expect both execute/match terminal output, while get_history and read_buffer both retrieve output. Descriptions provide guidance, but an agent could still misselect between them.

    Naming Consistency4/5

    Most tools follow a snake_case verb_noun pattern (get_history, list_sessions, switch_session, close_session, read_buffer, list_ports). A few single-word names (serial, spawn, send, status) deviate slightly but remain readable and predictable.

    Tool Count5/5

    12 tools is well within the ideal range for a terminal/serial session management server. Each tool covers a distinct operational area such as session creation, I/O, discovery, and health monitoring.

    Completeness4/5

    The surface covers core lifecycle operations: connect/spawn, list, switch, close, send, read, expect/exec, history, ports, and status. Minor gaps exist (e.g., explicit terminal resize or file transfer), but agents can work around them with existing tools.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources