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),…
Atera device monitors: HTTP, SNMP, and TCP monitor types for network devices, services, and applications, plus monitor configuration, thresholds, and polling behavior.
$ npx -y skills add wyre-technology/msp-claude-plugins --skill devices --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/devicesContext preview
The summary Claude sees to decide when to auto-load this skill.
Atera device monitors: HTTP, SNMP, and TCP monitor types for network devices, services, and applications, plus monitor configuration, thresholds, and polling behavior.
name: "Atera Devices" description: > Atera device monitors: HTTP, SNMP, and TCP monitor types for network devices, services, and applications, plus monitor configuration, thresholds, and polling behavior. when_to_use: >- When configuring or troubleshooting Atera network and device monitors. Use when: atera device, atera monitor, http monitor, snmp monitor, tcp monitor, network monitor, device monitoring, snmp polling, uptime monitoring, or port monitor.
Atera device monitors extend monitoring capabilities beyond agent-based endpoints to include network devices, services, and applications. These agentless monitors use HTTP, SNMP, and TCP protocols to check availability and gather metrics.
record, not a device monitor; use `atera-agents`. This is the single most common misroute in this plugin, because "device" means the managed endpoint in every other RMM here.
live here; the acknowledge/resolve lifecycle is `atera-alerts`.
— use `auvik-devices` or `auvik-networks`; this skill only configures Atera's own HTTP, SNMP, and TCP checks.
Monitor web services and applications via HTTP/HTTPS requests.
| Feature | Description | |---------|-------------| | **Protocol** | HTTP or HTTPS | | **Methods** | GET, POST, HEAD | | **Validation** | Status code, response content | | **Authentication** | Basic, custom headers | | **Use Cases** | Websites, APIs, web apps |
Monitor network devices using Simple Network Management Protocol.
| Feature | Description | |---------|-------------| | **Versions** | SNMP v1, v2c, v3 | | **Operations** | GET, GETNEXT, WALK | | **Data Types** | OIDs, MIBs, counters | | **Use Cases** | Routers, switches, firewalls, printers |
Monitor service availability via TCP port connectivity.
| Feature | Description | |---------|-------------| | **Protocol** | TCP | | **Check Type** | Port open/closed | | **Response** | Connection success/timeout | | **Use Cases** | Custom services, databases, mail servers |
| Field | Type | Description | |-------|------|-------------| | `DeviceID` | int | Unique device identifier | | `CustomerID` | int | Associated customer ID | | `CustomerName` | string | Customer display name | | `DeviceName` | string | Monitor display name | | `DeviceType` | string | HTTP, SNMP, TCP | | `Hostname` | string | Target host/IP address | | `Online` | boolean | Current status | | `LastSeen` | datetime | Last successful check | | `CreatedOn` | datetime | Monitor creation date |
| Field | Type | Description | |-------|------|-------------| | `URL` | string | Full URL to monitor | | `Port` | int | HTTP port (default 80/443) | | `CheckCertificateExpiration` | boolean | Monitor SSL cert | | `CheckCertificateRevocation` | boolean | Check cert revocation | | `Username` | string | Basic auth username | | `Password` | string | Basic auth password | | `ResponseText` | string | Expected response content | | `ResponseCode` | int | Expected HTTP status |
| Field | Type | Description | |-------|------|-------------| | `Port` | int | SNMP port (default 161) | | `Community` | string | SNMP community string | | `OID` | string | Object identifier to query | | `Threshold` | string | Alert threshold | | `ThresholdComparison` | string | Comparison operator |
| Field | Type | Description | |-------|------|-------------| | `Username` | string | SNMPv3 username | | `AuthProtocol` | string | MD5, SHA, SHA256, SHA384, SHA512 | | `AuthPassword` | string | Authentication password | | `PrivProtocol` | string | DES, AES, AES192, AES256 | | `PrivPassword` | string | Privacy password | | `ContextName` | string | SNMPv3 context |
| Field | Type | Description | |-------|------|-------------| | `Port` | int | TCP port to check | | `Timeout` | int | Connection timeout (ms) |
GET /api/v3/devices/generic?page=1&itemsInPage=50
X-API-KEY: {api_key}**Response:**
{
"items": [
{
"DeviceID": 55555,
"CustomerID": 12345,
"CustomerName": "Acme Corporation",
"DeviceName": "Core Router",
"DeviceType": "SNMP",
"Hostname": "192.168.1.1",
"Online": true,
"LastSeen": "2024-02-15T14:30:00Z"
}
],
"totalItems": 25,
"page": 1,
"itemsInPage": 50,
"totalPages": 1
}POST /api/v3/devices/http
X-API-KEY: {api_key}
Content-Type: application/json{
"CustomerID": 12345,
"DeviceName": "Website Monitor",
"Hostname": "www.acme.com",
"URL": "https://www.acme.com/health",
"Port": 443,
"CheckCertificateExpiration": true,
"ResponseCode": 200,
"ResponseText": "OK"
}**Response:**
{
"ActionID": 55556,
"DeviceID": 55556
}POST /api/v3/devices/snmp
X-API-KEY: {api_key}
Content-Type: application/json{
"CustomerID": 12345,
"DeviceName": "Core Router",
"Hostname": "192.168.1.1",
"Port": 161,
"Community": "public",
"OID": "1.3.6.1.2.1.1.3.0",
"Threshold": "1000",
"ThresholdComparison": ">"
}POST /api/v3/devices/snmpv3
X-API-KEY: {api_key}
Content-Type: application/json{
"CustomerID": 12345,
"DeviceName": "Firewall",
"Hostname": "192.168.1.254",
"Port": 161,
"Username": "snmpuser",
"AuthProtocol": "SHA256",
"AuthPassword": "authpass123",
"PrivProtocol": "AES256",
"PrivPassword": "privpass123",
"OID": "1.3.6.1.4.1.9.9.109.1.1.1.1.3.1",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…