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…
Huntress billing and summary reports: what each report type contains, the list/get tools for both, and the monthly reconciliation, QBR security summary, and cost-analysis workflows an MSP builds from them.
Claude Code
$ npx -y skills add wyre-ai/msp-claude-plugins --skill billing --agent claude-code
Codex
$ npx skills add wyre-ai/msp-claude-plugins --skill billing -a codex -y
Cursor
$ npx skills add wyre-ai/msp-claude-plugins --skill billing -a cursor -y
Gemini CLI
$ npx skills add wyre-ai/msp-claude-plugins --skill billing -a gemini-cli -y
GitHub Copilot
$ npx skills add wyre-ai/msp-claude-plugins --skill billing -a github-copilot -y
OpenCode
$ npx skills add wyre-ai/msp-claude-plugins --skill billing -a opencode -y
Windsurf
$ npx skills add wyre-ai/msp-claude-plugins --skill billing -a windsurf -y
name: "Huntress Billing" description: > Huntress billing and summary reports: what each report type contains, the list/get tools for both, and the monthly reconciliation, QBR security summary, and cost-analysis workflows an MSP builds from them. when_to_use: >- When pulling Huntress billing or summary reports for invoicing, reconciliation, or a client-facing security summary. Use when: huntress billing, huntress report, billing report, summary report, client invoice, or msp billing.
Huntress provides billing and summary reports for MSP partners. Billing reports detail per-organization agent counts for invoicing, while summary reports provide security posture overviews for client-facing communications.
Billing reports show agent counts per organization for a billing period. Use these for client invoicing and cost reconciliation.
Summary reports provide security posture overviews including incidents detected, escalations raised, and overall threat landscape — ideal for client QBRs and monthly security reviews.
huntress_billing_reports_list
Parameters:
**Example response:**
{
"billing_reports": [
{
"id": "bill-2026-02",
"period": "2026-02",
"generated_at": "2026-03-01T00:00:00Z",
"total_agents": 1250,
"organization_count": 45
}
],
"next_page_token": null
}huntress_billing_reports_get
Parameters:
**Example response:**
{
"billing_report": {
"id": "bill-2026-02",
"period": "2026-02",
"organizations": [
{
"id": "org-456",
"name": "Acme Corporation",
"agent_count": 150
},
{
"id": "org-789",
"name": "TechStart Inc",
"agent_count": 75
}
],
"total_agents": 1250
}
}huntress_summary_reports_list
Parameters:
huntress_summary_reports_get
Parameters:
**Example response:**
{
"summary_report": {
"id": "sum-2026-02",
"period": "2026-02",
"total_incidents": 23,
"total_escalations": 5,
"incidents_by_severity": {
"critical": 2,
"high": 8,
"low": 13
},
"top_threat_categories": [
"Persistent Footholds",
"Malicious Scripts",
"Unauthorized Access"
]
}
}1. List billing reports with `huntress_billing_reports_list` 2. Get the current period's report 3. Compare agent counts per organization with expected counts 4. Flag discrepancies for review 5. Generate invoices based on per-org agent counts
1. Get summary report for the review period 2. Get billing report for agent counts 3. List incidents filtered by organization 4. Compile per-client security posture summary 5. Present: agents protected, threats detected, incidents resolved
1. Pull billing reports for multiple periods 2. Track agent count trends per organization 3. Identify growing or shrinking clients 4. Forecast billing for upcoming periods
**Cause:** Report for the specified period hasn't been generated yet **Solution:** Check available reports with the list endpoint first
**Cause:** Account is new or billing hasn't been processed yet **Solution:** Reports are typically generated monthly; wait for the billing cycle
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.