MCP server intelligence profile

Windows CLI MCP Server

Enables secure command-line interactions on Windows systems with support for PowerShell, CMD, Git Bash, and WSL shells, providing controlled file access, command execution, and configurable security restrictions

Local Onlys2005
Awaiting current scanNpm · 1.3.1

The selected current version does not yet have completed public verification. Unknown does not mean clean or vulnerable.

1Distribution channel
6Independently observed tools
0Linked remote endpoints
AvailableVersion intelligence

Detailed security scan evidence is not public for this MCP yet. Public identity, registry metadata, and independently observed protocol inventory remain available.

Install and connect

Installation and connection instructions are shown only when supported by retained package, repository, or endpoint evidence.

Install wcli0 from npm

Version 1.3.1 declares 1 executable entrypoint.

npm install --save-exact wcli0@1.3.1
npx -y -p wcli0@1.3.1 wcli0
MCP client configuration example
{
  "mcpServers": {
    "wcli0": {
      "command": "npx",
      "args": [
        "-y",
        "-p",
        "wcli0@1.3.1",
        "wcli0"
      ]
    }
  }
}

Identity

Canonical slugwindows-cli-mcp-server-88e49e46DeploymentLocal Only
Canonical packagenpm:wcli0Repositorys2005/wcli0
First published—Latest release—
Last security verification—Classification confidence90%
PublicationDraftOfficial distributionNot verified

Distributions

ChannelIdentifierCurrent versionVersionsSource
npmwcli01.3.11Repository

Current release

PackageVersionPublished / observedInventorySecurity scan
npmwcli01.3.1CurrentSep 5, 20266 toolsSucceeded · 6 resources · 0 promptsEvidence restricted
Enterprise protection

Continuously monitor this MCP for security risk

Independently scan the exact version your agents use, receive alerts when its risk changes, and investigate every finding with retained version evidence.

  • Independent exact-version security scans
  • Continuous release and vulnerability monitoring
  • Risk-change alerts with capability context
  • Historical evidence and API exports
Custom pricingContact salesTailored to your organization, integrations, data needs, and support requirements.

Current version evidence

No public current-version evidence is available yet.

Current protocol inventory

2025-06-18Negotiated protocol
wcli0Server-reported name
2Capability groups
Aug 22, 2026Observed

Tools 6

ToolCategoryAnnotationsRisk
execute_commandExecute a command in the specified shell (powershell, cmd, gitbash, bash, wsl) **IMPORTANT GUIDELINES:** 1. ALWAYS use the `workingDir` parameter to specify the working directory 2. Request config of this MCP server configuration using tools 3. Follow limitations taken from configuration 4. Use validate_directories tool to validate directories before execution **Shell-Specific Settings:** **powershell:** - Command timeout: 30s - Max command length: 2000 characters - Injection protection: enabled - Blocked operators: &, |, ;, ` - Path format: Windows-style (C:\Users\...) **cmd:** - Command timeout: 30s - Max command length: 2000 characters - Injection protection: enabled - Blocked operators: &, |, ;, ` - Path format: Windows-style (C:\Users\...) **gitbash:** - Command timeout: 30s - Max command length: 2000 characters - Injection protection: enabled - Blocked operators: &, |, ;, ` - Path format: Mixed (C:\... or /c/...) **bash:** - Command timeout: 30s - Max command length: 2000 characters - Injection protection: enabled - Blocked operators: &, |, ;, ` - Path format: Unix-style (/home/user, /mnt/c/...) **wsl:** - Command timeout: 30s - Max command length: 2000 characters - Injection protection: enabled - Blocked operators: &, |, ;, ` - Path format: Unix-style (/home/user, /mnt/c/...) - Inherits global Windows paths (converted to /mnt/...) **Working Directory:** - If omitted, uses the server's current directory - Must be within allowed paths for the selected shell - Must use the correct format for the shell type **Output Truncation:** - Output is automatically truncated if it exceeds the configured limit - Current limit: 20 lines - Use `maxOutputLines` parameter to override the limit for a specific command - If truncated, use `get_command_output` tool with the executionId to retrieve full output - When file logging is enabled (via `logDirectory`), full logs are also saved to disk **Command Timeout:** - Each shell has a default command timeout (see Shell-Specific Settings above) - Use `timeout` parameter to override the timeout for a specific command - Timeout must be a positive integer between 1 and 3,600 seconds (1 hour) - If the timeout is exceeded, the command will be terminated **Examples:** Windows CMD: ```json { "shell": "cmd", "command": "dir /b", "workingDir": "C:\\Projects" } ``` WSL: ```json { "shell": "wsl", "command": "ls -la", "workingDir": "/home/user", "maxOutputLines": 50 } ``` With custom timeout: ```json { "shell": "wsl", "command": "long-running-command", "workingDir": "/home/user", "timeout": 120 } ``` Bash: ```json { "shell": "bash", "command": "ls -la", "workingDir": "/home/user", "maxOutputLines": 50 } ``` Git Bash: ```json { "shell": "gitbash", "command": "git status", "workingDir": "/c/Projects/repo" // or "C:\Projects\repo" } ``` With custom output limit: ```json { "shell": "gitbash", "command": "git log --oneline -50", "workingDir": "/c/Projects/repo", "maxOutputLines": 100 } ```
Input schema
{
  "type": "object",
  "properties": {
    "shell": {
      "type": "string",
      "enum": [
        "bash"
      ],
      "description": "Shell to use for command execution",
      "enumDescriptions": {
        "bash": "bash shell - timeout: 30s - Unix paths"
      }
    },
    "command": {
      "type": "string",
      "description": "Command to execute. Note: Different shells have different blocked commands and operators."
    },
    "workingDir": {
      "type": "string",
      "description": "Working directory (optional). Format depends on shell type:\n- Windows shells: Use C:\\Path\\Format\n- Unix/WSL shells: Use /unix/path/format\n- Mixed shells: Both formats accepted"
    },
    "maxOutputLines": {
      "type": "number",
      "description": "Maximum number of output lines to return (optional, overrides global setting). Must be a positive integer between 1 and 10,000."
    },
    "timeout": {
      "type": "number",
      "description": "Command timeout in seconds (optional, overrides global setting). Must be a positive integer between 1 and 3,600 (1 hour)."
    }
  },
  "required": [
    "shell",
    "command"
  ],
  "additionalProperties": false
}
——
get_command_outputRetrieve the full output from a previous command execution. Use this tool when command output was truncated and you need to see the complete result. The executionId is provided in the truncation message of the original command. Parameters: - executionId (required): The execution ID from the truncation message - startLine (optional): 1-based start line (default: 1) - endLine (optional): 1-based end line (default: last line) - search (optional): Regex pattern (case-insensitive) to filter lines - maxLines (optional): Maximum lines to return (default: config value) Examples: ```json { "executionId": "20251125-143022-a8f3" } ``` ```json { "executionId": "20251125-143022-a8f3", "startLine": 100, "endLine": 150 } ``` ```json { "executionId": "20251125-143022-a8f3", "search": "error|failed|exception" } ```
Input schema
{
  "type": "object",
  "properties": {
    "executionId": {
      "type": "string",
      "description": "Execution ID from a previous command (shown in truncation message)"
    },
    "startLine": {
      "type": "number",
      "description": "1-based start line (optional, default 1)"
    },
    "endLine": {
      "type": "number",
      "description": "1-based end line (optional, default last line)"
    },
    "search": {
      "type": "string",
      "description": "Regex pattern to filter lines (case-insensitive)"
    },
    "maxLines": {
      "type": "number",
      "description": "Maximum lines to return (default: config maxReturnLines)"
    }
  },
  "required": [
    "executionId"
  ],
  "additionalProperties": false
}
——
get_configGet the windows CLI server configuration **Returns:** - `global`: Default settings applied to all shells - `shells`: Enabled shells with any overrides applied Only enabled shells are included and technical fields like executables are omitted.
Input schema
{
  "type": "object",
  "properties": {}
}
——
get_current_directoryGet the current working directory
Input schema
{
  "type": "object",
  "properties": {}
}
——
set_current_directorySet the current working directory
Input schema
{
  "type": "object",
  "properties": {
    "path": {
      "type": "string",
      "description": "Path to set as current working directory"
    }
  },
  "required": [
    "path"
  ]
}
——
validate_directoriesCheck if directories are within allowed paths (only available when restrictWorkingDirectory is enabled) **Validation Modes:** - Global: Validates against server-wide allowed paths (default) - Shell-specific: Validates against a specific shell's allowed paths **Shell-Specific Validation:** Add the "shell" parameter to validate for a specific shell: ```json { "directories": ["/home/user", "/tmp"], "shell": "wsl" } ```
Input schema
{
  "type": "object",
  "properties": {
    "directories": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "List of directory paths to validate",
      "minItems": 1
    },
    "shell": {
      "type": "string",
      "enum": [
        "bash"
      ],
      "description": "Optional: Validate against a specific shell's allowed paths instead of global paths"
    }
  },
  "required": [
    "directories"
  ],
  "additionalProperties": false
}
——

Resources 6

  • bash Shell Configurationcli://config/shells/bash

    Resolved configuration for bash shell

  • CLI Server Configurationcli://config

    Complete server configuration with global and shell-specific settings

  • Command Execution Logs Listcli://logs/list

    List all stored command execution logs with metadata

  • Global Configurationcli://config/global

    Global default settings applied to all shells

  • Recent Command Logscli://logs/recent

    Get most recent command execution logs (supports ?n=<count> and ?shell=<shell>)

  • Security Informationcli://info/security

    Current security settings and restrictions

Resource templates 0

  • None observed.

Prompts 0

  • None observed.

Remote endpoints

EndpointTransportAuthenticationHealthObserved
No verified remote endpoint is linked.

Windows CLI MCP Server questions

How do I install Windows CLI MCP Server?

Install the selected package version with: npm install --save-exact wcli0@1.3.1

What tools does Windows CLI MCP Server provide?

Windows CLI MCP Server exposed 6 tools during independent protocol observation, including execute_command, get_command_output, get_config, get_current_directory, set_current_directory, validate_directories.

Is Windows CLI MCP Server secure?

The selected current version does not yet have completed public verification. Unknown does not mean clean or vulnerable.

Company and product intelligence

These internal links are derived from strong identity fields such as the implementation name, package, repository, vendor, and listing name—not generic description prose.

Associated company landscape

Microsoft & Azure intelligence →

Association is based on retained identity fields; it does not by itself prove first-party publication.

Windows 82 matches

Explore related MCP server guides

Curated product and capability guides containing this catalog record.

Official vs Community MCP Servers

Let’s talk about MCP security.

Share your details and our security team will contact you.