Skip to main content
Glama
LeandroPG19

Cuba-Exec

by LeandroPG19
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Cuba-Exec

No user-submitted related servers found.

    Related Servers

    • Shell MCP Server

      odysseus0
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that allows LLMs to execute shell commands and receive their output in a controlled manner.
      7
      MIT

    • 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
      153 npm
      6
      MIT

    • anthropic_skill

      williamchek
      F
      license
      Not graded
      quality
      D
      maintenance
      A robust, lightweight Model Context Protocol (MCP) server designed to empower your AI Agents with context-awareness, safe execution sandboxes, and dedicated thought logs.
      -

    • Shell-MCP

      kevinwatt
      A
      license
      B
      quality
      D
      maintenance
      A secure MCP server for executing whitelisted shell commands with resource and timeout controls, designed for integration with Claude and other MCP-compatible LLMs.
      20
      389 npm
      7
      MIT

    • terminal-mcp

      ParthKapoor-dev
      F
      license
      Not graded
      quality
      Not graded
      maintenance
      A secure and pluggable MCP server to run terminal commands on your local machine or cloud server — remotely, safely, and with LLMs or agentic clients.
      -
    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.1/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct operation: foreground execution, background start, status query, signal sending, stdin input, and process listing. No overlap in purpose, and the descriptions make the boundaries clear.

    Naming Consistency3/5

    There is a mix of conventions: 'status' is a noun, 'run' and 'start' are bare verbs, while 'send_signal', 'send_input', and 'list_processes' follow verb_noun. The send_* and list_* group is consistent, but the others break the pattern.

    Tool Count5/5

    Six tools cover the core process execution and management workflow without unnecessary bloat. The count feels well-scoped for this domain.

    Completeness5/5

    The set provides complete lifecycle coverage: synchronous execution, background starts, status checks, signal handling, stdin interaction, and process enumeration. No obvious gaps for a process execution server.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources