PowerShell.MCP v1.2.7 - Intelligent Encoding Management and Localized MCP Prompts #9
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.
-
Intelligent Encoding Management and Localized MCP Prompts
This release introduces intelligent encoding management that automatically upgrades ASCII files when adding non-ASCII content, along with localized MCP custom prompts for 17 languages.
✨ What's New
🔄 Automatic Encoding Upgrade
PowerShell.MCP now intelligently manages file encodings by automatically upgrading from ASCII to UTF-8 when non-ASCII characters are added:
Key Benefits:
🌐 Localized MCP Custom Prompts
MCP custom prompts are now localized for 17 languages (en-US, ja-JP, es-ES, fr-FR, de-DE, zh-CN, zh-TW, ko-KR, pt-BR, ru-RU, it-IT, nl-NL, pl-PL, tr-TR, ar-SA, hi-IN, sv-SE).
Example: "Software Development" → "ソフトウェア開発" (Japanese)
Note: Prompts are displayed in your operating system's display language.
🔄 Installation & Upgrade
Update MCP Configuration
(Get-Module PowerShell.MCP).ModuleBase{ "mcpServers": { "PowerShell": { "command": "C:\\Path\\To\\PowerShell.MCP\\1.2.7\\bin\\PowerShell.MCP.Proxy.exe" } } }📖 Full Guide: https://github.com/yotsuda/PowerShell.MCP#quick-start
💡 Usage Examples
Automatic Encoding Upgrade
Line Range Operations
Pattern-Based Updates
📊 What's Changed Since v1.2.6
New Features:
No Breaking Changes:
Full Documentation: https://github.com/yotsuda/PowerShell.MCP
Questions? GitHub Discussions
Report Issues: GitHub Issues
This discussion was created from the release PowerShell v1.2.7 - Intelligent Encoding Management and Localized MCP Prompts.
Beta Was this translation helpful? Give feedback.
All reactions