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…
Blumira resolution types (Valid, Not Applicable, False Positive): how to choose between them, their effect on security metrics and detection tuning, and the org- and MSP-level resolve calls.
Claude Code
$ npx -y skills add wyre-ai/msp-claude-plugins --skill resolutions --agent claude-code
Codex
$ npx skills add wyre-ai/msp-claude-plugins --skill resolutions -a codex -y
Cursor
$ npx skills add wyre-ai/msp-claude-plugins --skill resolutions -a cursor -y
Gemini CLI
$ npx skills add wyre-ai/msp-claude-plugins --skill resolutions -a gemini-cli -y
GitHub Copilot
$ npx skills add wyre-ai/msp-claude-plugins --skill resolutions -a github-copilot -y
OpenCode
$ npx skills add wyre-ai/msp-claude-plugins --skill resolutions -a opencode -y
Windsurf
$ npx skills add wyre-ai/msp-claude-plugins --skill resolutions -a windsurf -y
name: "Blumira Resolutions" description: > Blumira resolution types (Valid, Not Applicable, False Positive): how to choose between them, their effect on security metrics and detection tuning, and the org- and MSP-level resolve calls. when_to_use: >- When closing a Blumira finding and deciding its disposition. Use when: resolution type, resolve finding, false positive, valid finding, not applicable, or close finding.
Resolutions are the final disposition applied to findings when closing them. Choosing the correct resolution type is critical for accurate security metrics, detection tuning, and compliance reporting.
covers only the disposition decision at close. The rest of the lifecycle is `blumira-findings` (or `blumira-msp` for a client account).
catalogue and is unrelated to remediation actions; Blumira cannot isolate, block, or kill anything.
close-out language, entirely different mechanics (Huntress acts on the endpoint). Use `huntress-incidents`.
| Code | Label | Description | When to Use | |------|-------|-------------|-------------| | 10 | Valid | Confirmed real threat | The finding represents a genuine security event. Action was taken (blocked, remediated, etc.) | | 20 | Not Applicable | Doesn't apply | The detection is correct but irrelevant to this environment (e.g., policy doesn't apply to test lab) | | 30 | False Positive | Incorrect detection | The detection fired incorrectly — the activity was benign |
blumira_resolutions_list
Returns all resolution types with their codes, labels, and descriptions.
blumira_findings_resolve finding_id=<UUID> resolution_type=10 notes="Confirmed credential stuffing attack from IP 203.0.113.50. Account locked, password reset forced."
blumira_msp_findings_resolve account_id=<UUID> finding_id=<UUID> resolution_type=30 notes="False positive - scheduled backup job triggers this detection. Added to allowlist."
1. **Is the detected activity real?**
2. Always include detailed notes explaining the decision 3. For False Positives, note what the activity actually was to help with tuning
1. `blumira_findings_list` filtered by the specific detection rule 2. Review a sample to confirm all are false positives 3. Resolve each with resolution type 30 and consistent notes 4. Consider requesting a rule tuning in the Blumira portal
**Cause:** Resolution code is not 10, 20, or 30 **Solution:** Use `blumira_resolutions_list` to confirm valid codes.
**Cause:** Some resolution workflows may require notes **Solution:** Always provide descriptive notes for audit trail purposes.
One command to supercharge Claude Code for MSP workflows. Then restart Claude Code. That's it. Documentation: mcp.wyre.ai
3CX's native PBX MCP server: the per-PBX endpoint shape (every PBX is its own FQDN and its own OAuth authorization server — there…
3CX's live-operations surface: read-only visibility into active calls, recordings, voicemail, department and queue membership,…
3CX's read-only directory surface: resolving a caller by email or by exact extension, searching the PBX's own phonebooks,…
3CX's system-and-configuration surface: server time, PBX event log and application log search, service status, database schema…
Abnormal Security abuse mailbox cases: user-reported email submissions, case statuses and judgments, the case lifecycle, bulk and…
Abnormal Security message analysis: message retrieval, email header inspection, attachments, sender reputation, delivery context,…
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
Ask which skill or flow fits your situation. A router over the skills in this repo.