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),…
Pax8 orders: order retrieval, order line items, provisioning status and timelines, billing terms, and the order-to-subscription workflow.
$ npx -y skills add wyre-technology/msp-claude-plugins --skill orders --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/ordersContext preview
The summary Claude sees to decide when to auto-load this skill.
Pax8 orders: order retrieval, order line items, provisioning status and timelines, billing terms, and the order-to-subscription workflow.
name: "Pax8 Orders" description: > Pax8 orders: order retrieval, order line items, provisioning status and timelines, billing terms, and the order-to-subscription workflow. when_to_use: >- When viewing orders, tracking provisioning status, or following an order through to an active subscription. Use when: pax8 order, pax8 purchase, pax8 provision, pax8 buy, place order pax8, order status, order tracking, new subscription order, or pax8 ordering.
Orders in Pax8 are the mechanism for provisioning new cloud subscriptions for client companies. When an MSP needs to set up a new product for a client -- whether it is Microsoft 365 licenses, a security tool, or backup solution -- they create an order. The order contains one or more line items, each specifying a product, quantity, and billing term. Once submitted, the order is processed and, upon successful provisioning, creates one or more subscriptions.
event; the live licence state is `pax8-subscriptions`. An order that provisioned twelve months ago tells you nothing about today's seat count.
`pax8-invoices`.
distributor, not the client buying from the MSP. Client-facing quoting lives in `connectwise-cpq-quotes` or `autotask-quotes`.
`qbo-expenses` or `xero-invoices`; a Pax8 order is not a PO on the books.
| Tool | Description | Key Parameters | |------|-------------|----------------| | `pax8-list-orders` | List orders with optional filters | `page`, `size`, `companyId` | | `pax8-get-order-by-uuid` | Get a single order's details | `uuid` (required) |
Call `pax8-list-orders` with optional parameters:
**Example: List all orders for a company:**
**Example: List recent orders (first page):**
Call `pax8-get-order-by-uuid` with the `uuid` parameter.
**Example:**
Create Order --> Processing --> Provisioning --> Completed --> Subscription Created
|
PendingManual
(vendor action needed)| State | Description | |-------|-------------| | `Submitted` | Order received and being processed | | `Processing` | Order is being provisioned | | `Completed` | Order fulfilled; subscriptions created | | `Failed` | Order could not be provisioned | | `PendingApproval` | Awaiting MSP approval (self-service orders) | | `Cancelled` | Order was cancelled before completion |
Each order contains one or more line items. Each line item corresponds to a single product:
| Concept | Description | |---------|-------------| | Product | The cloud software being ordered | | Quantity | Number of seats/licenses | | Billing Term | Monthly, Annual, or Triennial | | Provision Start Date | When the subscription should begin |
1. **MSP creates an order** with line items for one or more products 2. **Pax8 processes the order** and initiates provisioning with the vendor 3. **Provisioning completes** (automated: seconds/minutes; manual: hours/days) 4. **Subscription is created** and becomes Active 5. **Billing begins** on the provision start date
| Field | Type | Required | Description | |-------|------|----------|-------------| | `id` | UUID | System | Order unique identifier | | `companyId` | UUID | Yes | Company the order is for | | `lineItems` | array | Yes | Products being ordered | | `status` | string | System | Current order status | | `createdDate` | datetime | System | When the order was placed | | `orderedBy` | string | System | Who placed the order |
| Field | Type | Required | Description | |-------|------|----------|-------------| | `id` | UUID | System | Line item unique identifier | | `productId` | UUID | Yes | Product being ordered | | `quantity` | integer | Yes | Number of licenses | | `billingTerm` | string | Yes | Billing term (Monthly, Annual) | | `provisionStartDate` | date | No | When subscription starts | | `lineItemNumber` | integer | System | Position in the order |
1. Call `pax8-get-order-by-uuid` with the order's `uuid` 2. Check the `status` field for the current state 3. Review each line item for product details and quantities 4. If status is not `Completed`, check back periodically
1. Find the company UUID using `pax8-list-companies` with `company_name` 2. Call `pax8-list-orders` with `companyId` and `size=200` 3. Paginate if needed to get all orders 4. Review order dates, statuses, and line items
1. After an order shows `Completed` status, call `pax8-list-subscriptions` with `companyId` 2. Look for subscriptions matching the ordered product IDs 3. Verify quantities and billing terms match the original order
When onboarding a new client, verify the typical stack was ordered:
1. Call `pax8-list-orders` with the `companyId` 2. Check that orders exist for the expected products (M365, security, backup) 3. Verify each order reached `Completed` status 4. Cross-reference with `pax8-list-subscriptions` to confirm active subscriptions
**Order:**
{
"id":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…