PowerShell.MCP v1.3.6 - Enhanced CLI Tool Color Support #20
yotsuda
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Enhanced CLI Tool Color Support
This release extends automatic color output support to additional CLI tools, improving the visual experience when working with modern development tools like GitHub CLI, .NET tools, and 24-bit color terminals.
✨ What's New
🌈 Extended Color Output Support
Added automatic color output for additional CLI tools commonly used in development workflows:
CLICOLOR_FORCECOLORTERMThese additions complement existing color support for Git, npm, yarn, cargo, and pytest, providing a consistent colorful experience across your entire toolchain.
📊 What's Changed Since v1.3.5
Core Enhancements
Environment Variables:
CLICOLOR_FORCE='1'for GitHub CLI and standard CLI toolsCOLORTERM='truecolor'for 24-bit color terminal supportDOTNET_SYSTEM_CONSOLE_ALLOW_ANSI_COLOR_REDIRECTION='1'for .NET toolsBehavior:
🔧 Technical Details: Color Environment Variables
PowerShell.MCP automatically configures the following environment variables to enable ANSI color output in MCP environments where stdout is redirected (not a TTY):
GIT_CONFIG_PARAMETERS'color.ui=always'FORCE_COLOR1NPM_CONFIG_COLORalwaysCARGO_TERM_COLORalwaysPY_COLORS1CLICOLOR_FORCE1COLORTERMtruecolorDOTNET_SYSTEM_CONSOLE_ALLOW_ANSI_COLOR_REDIRECTION1Configuration Behavior
if (-not $env:VARIABLE), respecting existing user configurations.Why These Variables Are Needed
When PowerShell captures output from external CLI tools (e.g., via pipes or variable assignment), those tools detect that their output is being redirected rather than displayed directly to a terminal. Most CLI tools disable ANSI color codes in this "non-interactive" mode to avoid cluttering logs with escape sequences. These environment variables override that detection, forcing tools to output color codes even when their stdout is redirected, ensuring colorful output is preserved for better readability and user experience.
📄 Installation & Upgrade
Update MCP Configuration
(Get-Module PowerShell.MCP).ModuleBase{ "mcpServers": { "PowerShell": { "command": "C:\\Users\\YourName\\Documents\\PowerShell\\Modules\\PowerShell.MCP\\1.3.6\\bin\\PowerShell.MCP.Proxy.exe" } } }Note: Adjust path as needed for your environment.
📖 Full Guide: https://github.com/yotsuda/PowerShell.MCP#quick-start
Full Documentation: https://github.com/yotsuda/PowerShell.MCP
Questions? GitHub Discussions
Report Issues: GitHub Issues
⚠ Security Notice: Provides complete PowerShell access. Use in trusted environments only.
This discussion was created from the release PowerShell.MCP v1.3.6 - Enhanced CLI Tool Color Support.
Beta Was this translation helpful? Give feedback.
All reactions