PSADT-MCP Server

A Model Context Protocol (MCP) server that provides AI assistants with powerful tools for Windows software deployment using the PowerShell App Deployment Toolkit (PSADT). This server enables AI assistants to help users create, manage, and deploy Windows applications with enterprise-grade deployment capabilities.

🚀 Features

• MSI Package Management: Extract information, deploy, and manage MSI installers
• EXE Deployment: Deploy executable installers with customizable parameters
• Winget Integration: Leverage Windows Package Manager for modern app deployments
• Deployment Verification: Validate successful installations and system state
• PSADT Integration: Full integration with PowerShell App Deployment Toolkit v4
• Dual Transport Support: Works with both STDIO and HTTP transports for maximum compatibility

🎯 Use Cases

• Automated Software Deployment: Create deployment scripts for enterprise environments
• Package Analysis: Extract metadata and requirements from MSI packages
• Installation Troubleshooting: Verify deployments and diagnose installation issues
• Winget Package Discovery: Find and deploy applications from the Windows Package Manager
• Enterprise App Management: Streamline software lifecycle management

📋 Prerequisites

Before setting up the PSADT-MCP server, ensure you have the following installed on your Windows system:

Required Software

• Windows 10/11: The server is designed for Windows environments
• PowerShell 5.1 or later: Required for PSADT functionality
• Node.js 18 or later: Runtime environment for the MCP server
  • Download from nodejs.org
  • Verify installation: node --version and npm --version

Optional but Recommended

• Windows Package Manager (winget): For modern package management
  • Usually pre-installed on Windows 11
  • For Windows 10: Install from Microsoft Store or GitHub releases
• Git: For cloning the repository and version control
  • Download from git-scm.com

System Requirements

• Administrator privileges: Required for software installation and deployment
• PowerShell execution policy: Set to allow script execution
  • Run as Administrator: Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope LocalMachine
• Disk space: At least 100MB for the toolkit and dependencies