Skip to content

ICC 0.1.1 — Windows / PSU 2026.3.3 community preview

Pre-release
Pre-release

Choose a tag to compare

@DataTraveler1 DataTraveler1 released this 14 Oct 01:52

I’ve built Incident Command Center (ICC) to demonstrate PowerShell Universal’s Model Context Protocol (MCP) feature with a small, working example.

Why does this exist?

ICC shows how a PowerShell workflow can become a tool that an external assistant discovers and calls through PSU’s MCP endpoint. PSU executes the PowerShell and stores the result; the assistant provides the conversation.

The ICC_Demo_Incident tool exposes Inspect, Acknowledge and Handoff. An assistant can read the current rehearsal, save receipt of its warning, verify the stored response and prepare a handoff from those facts. The dashboard makes the same saved state visible, so you can compare tool calls with direct app actions.

At fictional Acme Inc., a checkout latency warning gives the demonstration a simple scenario. The signals are synthetic; the acknowledgment is saved on the server. The native app also works independently of an MCP client.

ICC 0.1.1 is a single-server community preview for Windows with PSU and Devolutions.PowerShellUniversal 2026.3.3. Validation used PowerShell 7.6.6 and Codex CLI. Other platforms and clients remain untested. Acknowledgment records receipt of the warning; it performs no service repair.

Source, installation, MCP setup, recovery guidance and offline tests

MIT licensed. Use the dashboard to learn the rehearsal, then follow the MCP setup guide and try the same workflow through your assistant. Feedback and ideas for adapting the pattern are welcome.

Workflow screenshot

One saved acknowledgment, verified from disk, with a safe repeat and completed handoff.

Download IncidentCommandCenter-0.1.1.zip. The accompanying RELEASE-MANIFEST.json identifies the reviewed source and package; SHA256SUMS.txt supplies the matching checksums.