$ loading_
Let AI run CLI commands for deployment, inspection, and system administration.
This MCP tool requires no secrets and declares no fixed remote endpoints, and its source is open for review. The main security surface comes from its core capability—executing local CLI commands and scripts on behalf of an LLM—so it should be treated as a privileged local automation tool and used with caution rather than rated high risk based on current evidence.
The materials state that no keys or environment variables are required, and there is no indication that API tokens, account passwords, or other sensitive credentials must be supplied; based on the available information, the direct credential exposure surface appears low.
No fixed remote endpoint is declared, and the materials do not state that data is sent to any specific external service; however, because the tool can execute arbitrary CLI commands/scripts, the commands it runs could themselves initiate network connections, so potential egress paths still warrant caution.
Its core function is to let an LLM execute local CLI commands and scripts for deployment, system management, directory listing, and system information queries; this implies local process execution and system-level actions, which is a typical high-impact local execution surface, though the materials do not show additional red flags beyond that inherent capability.
Based on the description, the tool can at least access directory listings and system information; combined with CLI/script execution, the effective data access scope will generally depend on the operating system privileges of the MCP process, so it should be treated as a tool that may access local files and host information and should be run with constrained privileges.
Positive factors include being open source under the MIT License, which makes the code auditable and materially reduces opacity-related supply-chain risk; however, it comes from a third-party registry, has 0 stars, and shows unknown maintenance status, so confidence and maintenance evidence are limited and the repository and dependencies should be reviewed before use.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "cli-executor-mcp" yet — see the docs or source repo.
Inspect the current project directory, identify available deployment templates, and run the appropriate deployment steps for a Node.js app. Show the commands before executing them.
Provides directory and template inspection results, the commands to run, and a summary of deployment execution and outcomes.
Collect the current server's operating system, CPU, memory, disk usage, and basic network information, then format them into a concise inspection report.
Outputs key system metrics, summarized command results, and a readable inspection report.
List executable scripts in the scripts directory, run the log-cleanup and cache-cleanup scripts in sequence, and report status and errors after each step.
Returns the script list, step-by-step execution logs, success or failure status, and error details.
Turn almost any CLI tool into an MCP service for AI assistants.
Execute Linux commands and manage files for automated development and operations tasks.
Run and manage CLI commands in natural language with recursive help parsing.
Run LLM prompts and implement MCP client workflows from the command line.
Lets AI agents run Python, execute scripts, and install pip packages locally.
Control terminal, search files, and edit diffs for local dev workflows.