PowerShell.MCP v1.3.2 - Stability Fix + PowerShell.Map v1.0.1 Support #16
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.
-
Stability Fix + PowerShell.Map v1.0.1 Support
This release prioritizes engine stability by reverting the v1.3.1 stream capture feature and adds PowerShell.Map v1.0.1 support with 3D maps and location descriptions.
✨ What's New
🛡️ Engine Stability Restored
v1.3.1's complete stream capture (including Verbose and Debug) caused instability in production. This release reverts to the proven v1.3.0 implementation.
Trade-off:
Four critical streams remain captured: Success, Error, Warning, Information.
🗺️ PowerShell.Map v1.0.1 Support
Updated Create Interactive Map built-in prompt for PowerShell.Map v1.0.1 features:
📊 What's Changed Since v1.3.1
No Breaking Changes - All v1.3.1 scripts work unchanged.
🔄 Installation & Upgrade
Update MCP Configuration
(Get-Module PowerShell.MCP).ModuleBase{ "mcpServers": { "PowerShell": { "command": "C:\\Users\\YourName\\Documents\\PowerShell\\Modules\\PowerShell.MCP\\1.3.2\\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.2 - Stability Fix + PowerShell.Map v1.0.1 Support.
Beta Was this translation helpful? Give feedback.
All reactions