PowerShell.MCP v1.4.1 - Syntax Highlighting & Stability Improvements #26
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.
-
PowerShell.MCP v1.4.1 - Syntax Highlighting & Startup Banner
This release improves syntax highlighting accuracy, prevents conflicts from multiple server instances, and adds customizable startup banners.
🎉 What's New
Startup Banner
The
start_powershell_consoletool now accepts an optionalbannerparameter to display a customizable message when the PowerShell console launches. AI assistants can use this to add personality with greetings, jokes, or fun facts!Single Instance Enforcement
PowerShell.MCP now detects if another server is already running and fails module import with a clear error message. This prevents confusion from orphaned sessions or duplicate servers.
Detection uses a connection test to the named pipe/socket, which works reliably on all platforms.
📊 What's Changed Since v1.4.0
New Features
start_powershell_consolenow supports abannerparameter for custom startup messages (displayed in green)Improvements
Internal
-Targetparameter for selective builds (Dll, WinX64, LinuxX64, OsxX64, OsxArm64)📄 Installation & Upgrade
Windows
Linux / macOS
Update MCP Configuration
{ "mcpServers": { "PowerShell": { "command": "C:\\Users\\YourName\\Documents\\PowerShell\\Modules\\PowerShell.MCP\\1.4.1\\bin\\win-x64\\PowerShell.MCP.Proxy.exe" } } }📖 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.4.1 - Syntax Highlighting & Stability Improvements.
Beta Was this translation helpful? Give feedback.
All reactions