CLI Exec

CLI Exec

jakenuts

Executes shell commands with structured output including exit codes, stdout/stderr, and error handling. Provides both raw command execution and multi-command workflows in specific directories.

Provides powerful CLI command execution capabilities, enabling structured output for shell commands with features like timeout handling, ANSI code stripping, and error management for system administration and DevOps workflows.

9502 views3Local (stdio)

What it does

  • Execute shell commands with timeout handling
  • Run multiple commands in sequence within a working directory
  • Strip ANSI codes from command output
  • Return structured results with exit codes and execution duration
  • Handle command errors gracefully
  • Stop execution on first command failure

Best for

System administrators automating server tasksDevOps engineers building deployment workflowsDevelopers running build scripts and testsInfrastructure automation and monitoring
Cross-platform command executionStructured output with detailed metadataConfigurable timeouts up to 5 minutes

About CLI Exec

CLI Exec is a community-built MCP server published by jakenuts that provides AI assistants with tools and capabilities via the Model Context Protocol. CLI Exec offers a powerful CLI interface for command line execution, with timeout, ANSI code stripping, and error handli It is categorized under developer tools. This server exposes 2 tools that AI clients can invoke during conversations and coding sessions.

How to install

You can install CLI Exec in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.

License

CLI Exec is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.

Tools (2)

cli-exec-raw

Execute a raw CLI command and return structured output

cli-exec

Execute one or more CLI commands in a specific working directory

mcp-cli-exec MCP Server

A powerful CLI command execution MCP server that enables running shell commands with structured output. This package focuses specifically on command execution functionality, differentiating it from other MCP CLI tools.

Features

Tools

cli-exec-raw

Execute a raw CLI command and return structured output

  • Takes a command string and optional timeout (default: 5 minutes)
  • Returns detailed execution results including stdout, stderr, exit code
  • Handles errors gracefully with structured error responses

cli-exec

Execute one or more CLI commands in a specific working directory

  • Supports single commands, && chained commands, or array of commands
  • All commands execute in the specified working directory
  • Returns detailed results for each command:
    • Success/failure status
    • Exit code
    • stdout and stderr (ANSI codes stripped)
    • Execution duration
    • Working directory
  • Stops on first command failure
  • Optional timeout per command (default: 5 minutes)

Note: Due to execution context limitations, each command runs independently. Directory changes (cd) within commands do not affect subsequent commands. All commands execute in the initially specified working directory.

Output Format

Commands return structured results including:

  • Success/failure status
  • Exit code
  • stdout and stderr (with ANSI codes stripped)
  • Execution duration
  • Working directory
  • Detailed error information if applicable

Example Usage

cli-exec-raw

Simple command execution:

{
  "command": "echo Hello World"
}

With timeout:

{
  "command": "long-running-script.sh",
  "timeout": 300000
}

cli-exec

Single command in specific directory:

{
  "workingDirectory": "/path/to/project",
  "commands": "npm install"
}

Multiple commands (all run in the same working directory):

{
  "workingDirectory": "C:\\project",
  "commands": [
    "dir /b",
    "npm run build"
  ]
}

Installation

Optionally install from npm:

npm install -g mcp-cli-exec
# or with pnpm
pnpm add -g mcp-cli-exec

Or just use npx in your configuration

For Cline VSCode Extension

Add to %APPDATA%/Code - Insiders/User/globalStorage/rooveterinaryinc.roo-cline/settings/cline_mcp_settings.json:

{
  "mcpServers": {
    "mcp-cli-exec": {
      "command": "npx",
      "args": ["-y", "mcp-cli-exec"]
    }
  }
}

For Claude Desktop

Add to the appropriate config file:

Windows: %APPDATA%/Claude/claude_desktop_config.json MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "mcp-cli-exec": {
      "command": "npx",
      "args": ["-y", "mcp-cli-exec"]
    }
  }
}

Special Windows Configuration

If you encounter the ENOENT spawn npx issue on Windows, use this alternative configuration that specifies the full paths:

{
  "mcpServers": {
    "mcp-cli-exec": {
      "command": "C:\\Users\\jim\\AppData\\Roaming\\nvm\\v22.1.0\\node.exe",
      "args": [
        "C:\\Users\\jim\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npx-cli.js",
        "-y",
        "mcp-cli-exec"
      ]
    }
  }
}

Development

Install dependencies:

pnpm install

Build the server:

pnpm run build

For development with auto-rebuild:

pnpm run watch

Debugging

Since MCP servers communicate over stdio, debugging can be challenging. The MCP Inspector provides helpful debugging tools:

pnpm run inspector

This will provide a URL to access the inspector in your browser, where you can:

  • View all MCP messages
  • Inspect request/response payloads
  • Test tools interactively
  • Monitor server state

Error Handling

The server includes comprehensive error handling:

  • Input validation for all tool parameters
  • Structured error responses
  • Command timeout handling
  • Working directory validation
  • ANSI code stripping for clean output

Technical Details

  • Built with TypeScript and the MCP SDK
  • Uses execa for reliable command execution
  • Default command timeout: 5 minutes
  • Supports Windows and Unix-like systems (use appropriate commands for your OS, e.g., 'dir' vs 'ls')
  • Executes commands sequentially, stopping on first failure
  • Each command runs independently in the specified working directory

Alternatives

Related Skills

Browse all skills
cli-builder

Guide for building TypeScript CLIs with Bun. Use when creating command-line tools, adding subcommands to existing CLIs, or building developer tooling. Covers argument parsing, subcommand patterns, output formatting, and distribution.

2
codex-cli-bridge

Bridge between Claude Code and OpenAI Codex CLI - generates AGENTS.md from CLAUDE.md, provides Codex CLI execution helpers, and enables seamless interoperability between both tools

2
mcp-developer

Use when building MCP servers or clients that connect AI systems with external tools and data sources. Invoke for MCP protocol compliance, TypeScript/Python SDKs, resource providers, tool functions.

0
cli-developer

Use when building CLI tools, implementing argument parsing, or adding interactive prompts. Invoke for CLI design, argument parsing, interactive prompts, progress indicators, shell completions.

0
azure-identity-rust

Azure Identity SDK for Rust authentication. Use for DeveloperToolsCredential, ManagedIdentityCredential, ClientSecretCredential, and token-based authentication. Triggers: "azure-identity", "DeveloperToolsCredential", "authentication rust", "managed identity rust", "credential rust".

0
mcp-management

Manage Model Context Protocol (MCP) servers - discover, analyze, and execute tools/prompts/resources from configured MCP servers. Use when working with MCP integrations, need to discover available MCP capabilities, filter MCP tools for specific tasks, execute MCP tools programmatically, access MCP prompts/resources, or implement MCP client functionality. Supports intelligent tool selection, multi-server management, and context-efficient capability discovery.

0