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),…
runZero wireless network discovery: discovered wireless networks, rogue access point identification, wireless security configuration analysis, and SSID auditing.
$ npx -y skills add wyre-technology/msp-claude-plugins --skill wireless --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/wirelessContext preview
The summary Claude sees to decide when to auto-load this skill.
runZero wireless network discovery: discovered wireless networks, rogue access point identification, wireless security configuration analysis, and SSID auditing.
name: "runZero Wireless" description: > runZero wireless network discovery: discovered wireless networks, rogue access point identification, wireless security configuration analysis, and SSID auditing. when_to_use: >- When auditing wireless networks or hunting rogue access points discovered by runZero. Use when: runzero wireless, wireless network, wifi discovery, rogue ap, rogue access point, wireless security, ssid, wireless audit, or wifi scan.
RunZero discovers wireless networks visible from explorer locations, including authorized corporate networks, guest networks, and potential rogue access points. Wireless discovery helps MSPs maintain visibility into the RF environment and identify unauthorized network infrastructure.
RF a nearby explorer can hear; it cannot change an SSID, PSK, channel, or radio setting, and it has no view of client roaming or throughput. Wireless configuration and client troubleshooting are `meraki-devices` and `meraki-troubleshooting`.
is `runzero-assets`; its uplink and switch port are `auvik-devices`.
Each discovered wireless network includes:
| Attribute | Description | |-----------|-------------| | `essid` | The network name (SSID) | | `bssid` | The access point MAC address | | `channel` | The wireless channel | | `encryption` | Security protocol (WPA2, WPA3, WEP, Open) | | `signal` | Signal strength | | `type` | Infrastructure or ad-hoc | | `vendor` | AP hardware vendor (from OUI lookup) | | `first_seen` | When the network was first discovered | | `last_seen` | When the network was last observed | | `site_id` | The site where the network was detected |
| Encryption | Security Level | Notes | |------------|---------------|-------| | WPA3 | Strong | Recommended standard | | WPA2-Enterprise | Strong | Requires RADIUS | | WPA2-Personal | Moderate | Vulnerable to offline brute force | | WPA | Weak | Deprecated; upgrade recommended | | WEP | Critical | Trivially breakable; must replace | | Open | None | No encryption; use only for guest with captive portal |
A rogue access point is an unauthorized AP connected to the corporate network. Indicators include:
runzero_wireless_list
Parameters:
**Example response:**
{
"wireless": [
{
"id": "wireless-uuid-123",
"essid": "ACME-Corporate",
"bssid": "AA:BB:CC:DD:EE:FF",
"channel": 6,
"encryption": "WPA2-Enterprise",
"signal": -45,
"vendor": "Cisco Meraki",
"type": "infrastructure",
"first_seen": "2026-01-15T10:00:00Z",
"last_seen": "2026-03-27T08:30:00Z",
"site_id": "site-uuid-456"
}
]
}runzero_wireless_get
Parameters:
1. List all wireless networks for a site: `runzero_wireless_list` 2. Check encryption types -- flag WEP, WPA, and Open networks 3. Identify networks with weak security 4. Recommend upgrades to WPA2-Enterprise or WPA3 5. Generate a wireless security posture report
1. Export all wireless networks for the site 2. Compare BSSIDs against the authorized AP inventory 3. Flag unknown BSSIDs as potential rogues 4. Check for SSID spoofing (matching corporate SSID with unknown BSSID) 5. Investigate vendor and location of suspicious APs 6. Report findings with recommended actions
1. List all wireless networks across sites 2. Group by SSID, encryption type, and vendor 3. Count unique access points per site 4. Generate per-client wireless infrastructure summary
1. Export wireless networks for a site 2. Group by channel 3. Identify channels with multiple APs (potential interference) 4. Recommend channel planning adjustments
**Cause:** Explorer does not have a wireless adapter, or wireless scanning is disabled **Solution:** Verify explorer has wireless capability; enable wireless scanning in scan configuration
**Cause:** Explorer can only detect APs within radio range **Solution:** Deploy explorers at multiple physical locations for comprehensive coverage
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…