api-patterns
3CX's native PBX MCP server: the per-PBX endpoint shape (every PBX is its own FQDN and its own OAuth authorization server — there is no shared mcp.3cx.com),…
Working the clustermgmt namespace through `clustermgmt_execute` — cluster and host inventory, configuration and health state — plus the adjacent read surfaces: `prism_execute` for Prism Central tasks and categories, and `lifecycle_execute` for LCM upgrade inventory and
$ npx -y skills add wyre-technology/msp-claude-plugins --skill cluster-operations --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/cluster-operationsContext preview
The summary Claude sees to decide when to auto-load this skill.
Working the clustermgmt namespace through `clustermgmt_execute` — cluster and host inventory, configuration and health state — plus the adjacent read surfaces: `prism_execute` for Prism Central tasks and categories, and `lifecycle_execute` for LCM upgrade inventory and
name: "Nutanix Cluster Operations" description: > Working the clustermgmt namespace through `clustermgmt_execute` — cluster and host inventory, configuration and health state — plus the adjacent read surfaces: `prism_execute` for Prism Central tasks and categories, and `lifecycle_execute` for LCM upgrade inventory and recommendations. when_to_use: >- When inspecting Nutanix clusters, hosts, or Prism Central itself. Use when: nutanix cluster, cluster health nutanix, host inventory nutanix, clustermgmt, prism central tasks, lcm inventory, nutanix upgrade status, or nutanix cluster configuration.
Cluster-level work spans three namespaces. `clustermgmt` is the core: clusters, hosts/nodes, cluster profiles, and storage container associations. `prism` covers Prism Central's own surface — tasks, categories, cluster registration state. `lifecycle` exposes LCM (Lifecycle Manager) inventory: what software/firmware versions each cluster runs and what upgrades LCM recommends. Each is reached through its own executor after discovery.
| Concept | Namespace | Notes | |---------|-----------|-------| | Cluster | `clustermgmt` | Config, health state, nodes, network config; identified by `extId` | | Host / node | `clustermgmt` | Physical servers in a cluster; disk and NIC detail per host | | Task | `prism` | Async operations on PC; status is `QUEUED` / `RUNNING` / `SUCCEEDED` / `FAILED` | | Category | `prism` | key:value tags shared by VMs, hosts, policies | | LCM entity | `lifecycle` | An upgradeable component with current and available versions |
1. `listOperations(namespace="clustermgmt", search="clusters")` → list-clusters operation. 2. `clustermgmt_execute` to list clusters; capture name, `extId`, version, node count. 3. For each cluster of interest, get it by `extId` for config and health detail, and list its hosts for per-node state. 4. Fold in open alerts from the `monitoring` namespace (see the monitoring-aiops skill) for a complete health picture.
1. Discover the list-tasks operation in `prism`. 2. `prism_execute` with an OData filter, e.g. `_filter="status eq 'FAILED'"` plus a time-range predicate, ordered by start time. 3. Report each task's `extId`, operation type, error messages, and timing.
1. `listOperations(namespace="lifecycle", search="entities")` to find the LCM inventory operation; `lifecycle_execute` to list current component versions per cluster. 2. Discover and read LCM recommendations to see upgrade candidates and blocking pre-check conditions. 3. Stop there: performing upgrades, pre-checks that mutate state, and node imaging are non-GET and blocked by read-only mode. Deliver the findings as an upgrade plan for a human to execute.
`listOperations` with a `search` term; paging the whole namespace wastes turns.
cluster-side container associations; `storage` is the primary container/volume surface. Prefer `storage` for capacity questions.
`clustermgmt` lists may simply not be registered with this Prism Central — check registration state via `prism` before declaring it down.
One command to supercharge Claude Code for MSP workflows. Then restart Claude Code. That's it. Documentation: mcp.wyre.ai
Repo: wyre-technology/msp-claude-plugins
3CX's native PBX MCP server: the per-PBX endpoint shape (every PBX is its own FQDN and its own OAuth authorization server — there is no shared mcp.3cx.com),…
3CX's live-operations surface: read-only visibility into active calls, recordings, voicemail, department and queue membership, and forwarding/presence…
3CX's read-only directory surface: resolving a caller by email or by exact extension, searching the PBX's own phonebooks, searching contacts synced from an…
3CX's system-and-configuration surface: server time, PBX event log and application log search, service status, database schema and the read-only SELECT-only…
Abnormal Security abuse mailbox cases: user-reported email submissions, case statuses and judgments, the case lifecycle, bulk and remediation actions, and…
Abnormal Security message analysis: message retrieval, email header inspection, attachments, sender reputation, delivery context, and SPF/DKIM/DMARC…