Repository navigation
Connect your AI service to PowerShell Universal with MCP. Ask questions in plain English and use the PowerShell tools you choose to expose. An MCP-capable client connects the AI service to PSU; PSU runs the selected PowerShell on the server and returns the result for the service's reply.
Incident Command Center (ICC) is a working example of that connection. Its ICC_Demo_Incident tool lets you inspect a fictional Acme incident, save an acknowledgment, repeat it safely and prepare a handoff. The dashboard shows the same saved state. Signals are synthetic, and acknowledgment does not repair a service.
You can use a commercial AI service or an application connected to an LLM your organization provides. Either route needs an MCP-capable client that supports PSU's remote HTTP endpoint and app-token authentication, plus a model that can use tools. Familiar documented options include GitHub Copilot in VS Code, Codex and Claude Code. Only Codex has been tested with ICC. Other clients and organization-provided model setups need validation in your environment.
ICC 0.1.3 is a regular release for Windows with PSU and Devolutions.PowerShellUniversal 2026.3.3. It remains a single-server learning example; a regular release does not establish production readiness or compatibility with other environments.
This version binds native Acknowledge, Verify and Handoff buttons to the rehearsal displayed in their tab. Superseded tabs are rejected before acting on another rehearsal. It includes the 0.1.2 timeline-concurrency, missing-acknowledgment recovery and truthful initial-Verify corrections. See change history.
Validation recorded October 15, 2026 UTC on Windows Server 2019, PSU/module 2026.3.3, PowerShell 7.6.6 and Codex CLI 0.162.0-alpha.17.2:
- 338 offline checks, including 71 simulated installer scenarios, plus 47 server recovery/concurrency checks passed.
- Actual native use, safe repetition, saved-state verification, handoff and all three stale-tab rejections passed.
- One signed-in Codex conversation made six native HTTP MCP calls. Returned results, stored Completed PSU jobs and model facts/handoff agreed.
- On a separately refreshed PSU instance, both unchanged packaged installers passed with standard ICC names and an empty code/data path after residual folders were preserved. Native use and one installed-tool Inspect matched the same saved state and Completed job output. No new model session was run in that clean-install phase.
Linux, other PSU releases or clients, custom service identities and multiple nodes remain untested. PowerShell 7.5.4 is the package minimum. The acknowledgment is durable; the service signals are fixed demo data.
Install and use ICC · MCP setup · Updating and recovery · Native workflow screenshot
The AI introduction, repository description and main-branch guides were updated on October 15, 2026 after release. The v0.1.3 tag, downloadable package and dated validation scope are unchanged; the package retains its original reviewed documentation.
Download IncidentCommandCenter-0.1.3.zip below. It has one outer package directory containing the installers beside the module directory, docs and tests. RELEASE-MANIFEST.json identifies the exact source commit and every payload hash; SHA256SUMS.txt covers the payload, ZIP and manifest. Existing installations should follow the updating/recovery guide instead of rerunning the fresh installers. Earlier tags, releases and assets are retained. MIT licensed.