Commandry MCP Version 1.0.0
Release Date: November 13, 2025
🔧 Improvements
- Full MCP protocol support: Added complete support for Resources, Prompts, Sampling, Roots, Elicitation, and Instructions capabilities
- Progress reporting: Added support for progress updates from long-running PowerShell scripts via
Write-Progresscommand - Standardized logging: Implemented logging support for
Write-{Level}commands to send logs to MCP client - Log verbosity control: Added
--log-verbositycommand-line option to control log output levels (Alert, Critical, Debug, Emergency, Error, Info, Notice, Warning) - Prompt-based authoring: Simplified MCP capability authoring with dedicated prompt templates (mcptool, mcpprompt, mcpresourcelist, mcpresourcecontent, mcpresourcetemplatelist)
- Enhanced capability discovery: Generalized script and function discovery to support multiple MCP capability types beyond just tools
- PowerShell module reloading: Added automatic reloading of PowerShell modules on changes
🐛 Bug Fixes
- Schema generation: Fixed empty parameter descriptions in tool schema
- Command-line help: Clarified
--scan-directoryand--scan-moduledescriptions by removing restrictive.ROLErequirement mentions - HTTP endpoint: Corrected HTTP endpoint URL documentation (changed from
http://localhost:<port>/ssetohttp://localhost:<port>)
Getting Started
- Download and extract the release package
- Prepare PowerShell scripts with comment-based help including
.ROLEset to "MCP tool" - Run with directory scanning:
commandry-mcp-stdio --scan-directory /path/to/scripts - Or scan PowerShell modules:
commandry-mcp-stdio --scan-module MyModule - Connect your AI assistant using MCP client configuration
Usage Examples
STDIO Transport
# Scan a single directory
commandry-mcp-stdio --scan-directory <path-to-scripts>
# Scan multiple directories
commandry-mcp-stdio --scan-directory <path1> --scan-directory <path2>
# Scan PowerShell modules
commandry-mcp-stdio --scan-module <module-name-or-path>
# Combine directory and module scanning
commandry-mcp-stdio --scan-directory <path-to-scripts> --scan-module <module-name-or-path>See README.md for detailed documentation.