Skip to main content
Glama
clalarco

MCP CLI Server

by clalarco
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to MCP CLI Server

No user-submitted related servers found.

    Related Servers

    • mcp-infra

      DerWolk
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides tools for filesystem, database, web, system, and shell operations, along with resources and prompts via SSE transport.
      -

    • DevServer MCP

      Uninen
      A
      license
      Not graded
      quality
      F
      maintenance
      An MCP server that enables programmatic management and monitoring of development servers through a unified interface and interactive TUI. It provides tools for process control, log streaming, and experimental browser automation via Playwright.
      1
      MIT

    • bg-server-mcp-shell

      bgbruno
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for running long-running processes in PTY with real-time output streaming, enabling interactive dev servers, watch modes, and CLI tools.
      5 npm
      MIT

    • vps-ops-mcp

      WillyV347
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for monitoring and managing long-running processes on a remote VPS via SSH, with tools for status, logs, record summaries, and arbitrary command execution.
      6 npm
      MIT

    • tcpsh-mcp

      nchgroup
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for interactive TCP connection management, enabling opening listeners, managing sessions, port forwarding, proxy with logging, and local command execution from any MCP host.
      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

    Disambiguation4/5

    Tools are mostly distinct: get_processes lists all, is_alive checks status, start/stop manage lifecycle, read_output reads current output, wait_for_output waits for pattern, write_input sends text. Some minor overlap exists between read_output and wait_for_output, but they serve different purposes (immediate read vs. waiting).

    Naming Consistency4/5

    All tool names use snake_case with a verb_noun pattern (e.g., start_program, stop_program). 'is_alive' deviates slightly (adjective_noun) but is still clear. Overall consistent enough for easy prediction.

    Tool Count5/5

    8 tools is an ideal number for a CLI process management server. Each tool covers a distinct aspect without bloat, making the surface easy to navigate.

    Completeness4/5

    Covers core lifecycle (start, stop, list, check status), I/O (write, read, wait for pattern). Lacks a restart or signal-sending tool, but the set is sufficient for most interactive CLI use cases.

    Resources