Cross-vendor incident correlation workflow

[asachs01]

Problem

Today each MCP server operates independently. A tech investigating an incident has to manually switch between vendors (PSA for the ticket, RMM for the device, docs platform for configs).

Proposed solution

Build a higher-level workflow that correlates data across vendors automatically:

1. Start with a ticket (PSA)
2. Identify the related device (RMM)
3. Pull configuration docs (IT Glue / Liongard)
4. Present a unified incident summary

This could be a Claude Code skill or a gateway-level feature that orchestrates multiple MCP calls.

Why this matters

This is the "killer feature" — the reason to connect multiple tools to Claude instead of just one. Early cowork testing with Datto RMM shows the individual pieces work; now we need the orchestration layer.

[asachs01]

For anyone following this — the cross-vendor correlation workflow is a key priority. The individual MCP servers already provide the building blocks; what's needed is the orchestration layer that ties them together.

For discussion on how this should work and early prototyping, join us on Discord: https://discord.com/invite/cCPtPaFw8e

[asachs01]

Already resolved. Commit 793f660 ("feat(shared): add cross-vendor incident correlation skill and command (#20)", 2026-02-23) shipped exactly what this issue asked for: msp-claude-plugins/shared/skills/incident-correlation/SKILL.md (the 6-step PSA ticket → RMM device state → documentation platform (IT Glue/Hudu) → Liongard config-change correlation → unified incident summary workflow) plus the /correlate-incident command, both still present at current main (94c87de) and registered in shared/.claude-plugin/plugin.json's skills list. Looks like the commit's PR-number reference in its subject didn't auto-close this issue at merge time. Closing now — reopen if the ask was for something beyond what's shipped (e.g. a gateway-level orchestration feature rather than a Claude Code skill).