Devolutions PowerShell Universal
The Devolutions PowerShell Universal extension provides seamless integration between Visual Studio Code and PowerShell Universal, enabling you to browse, edit, and manage your PowerShell Universal configuration repositories directly from VS Code.
Key Features
- PowerShell Universal Activity View: Access a dedicated activity view to manage and organize your PowerShell Universal connections.
- Secure Connection Management: Store connection metadata in VS Code global state and App Tokens in SecretStorage for secure access.
- Direct Repository Editing: Open PowerShell Universal repositories as editable workspace folders using a custom
psu: file system, allowing you to work with configuration files as if they were local.
- Full File Operations: Create, delete, rename, and move configuration files and folders through the PowerShell Universal configuration API endpoints.
- Integrated Save Workflow: Edit and save files using the standard VS Code editor experience, with changes synchronized directly to your PowerShell Universal instance.
- Conflict Detection: Prevent stale editor contents from overwriting configuration files that changed on the server after they were opened.
- Debugger Integration: Surface local PowerShell Universal breakpoint candidates in a Debugger tree node and attach to them using the PowerShell VS Code extension for advanced debugging scenarios.
Getting Started
- Open the PowerShell Universal activity view in VS Code.
- Run the
PSU: Add Connection command.
- Enter a connection name, the PowerShell Universal base URL, and an App Token.
- Open your saved connection to add the PowerShell Universal repository as a workspace folder.
- Browse, edit, and manage configuration files directly from the Explorer, saving changes as needed.
Use the URL where PowerShell Universal is hosted, including any IIS application or reverse-proxy path, such as https://psu.example.com/Beta or https://psu.example.com/sites/Beta. A trailing slash is optional. Do not append /api or /api/v1/mcp; the extension adds its API routes to the base URL.
For local developer connections discovered through PowerShell Universal named-pipe discovery, the activity view also displays a Debugger category. You can view runspaces that are stopped at breakpoints and attach to them using the PowerShell extension's built-in debugger.
When PowerShell Universal workspace folders are open, the extension manages VS Code's Auto Save setting to ensure your workflow is optimized for configuration editing.
MCP Server Name
PowerShell Universal advertises Universal.Server as its MCP server name by default. To distinguish server connections in VS Code, set Mcp:ServerName in the server configuration (or the Mcp__ServerName environment variable) to an environment-specific value such as Production PSU.
Requirements
- A reachable PowerShell Universal instance
- A user or token with access to the configuration endpoints
- PowerShell Universal configuration API support at
/api/v1/configuration
- PowerShell Universal configuration API ETag support is required for stale-write protection.
- The PowerShell VS Code extension for debugger attach support