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),…
Autotask ticket notes, attachments, and charges — the secondary entities attached to tickets: retrieving/searching notes and attachments, and creating, updating, or searching ticket charges for labor and expenses billed directly to a ticket.
$ npx -y skills add wyre-technology/msp-claude-plugins --skill ticket-notes-attachments --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/ticket-notes-attachmentsContext preview
The summary Claude sees to decide when to auto-load this skill.
Autotask ticket notes, attachments, and charges — the secondary entities attached to tickets: retrieving/searching notes and attachments, and creating, updating, or searching ticket charges for labor and expenses billed directly to a ticket.
name: "Autotask Ticket Notes & Attachments" description: >- Autotask ticket notes, attachments, and charges — the secondary entities attached to tickets: retrieving/searching notes and attachments, and creating, updating, or searching ticket charges for labor and expenses billed directly to a ticket. when_to_use: >- When retrieving ticket notes, downloading ticket attachments, or managing ticket charges. Use when: autotask ticket note, autotask ticket attachment, autotask ticket charge, get ticket note autotask, download ticket attachment, ticket charges autotask, autotask labor charge, autotask ticket charges, search ticket notes autotask, or search ticket attachments autotask.
Beyond the core ticket record, Autotask tickets accumulate notes (internal/external communications), file attachments, and charges (labor and expenses billed directly to a ticket). This skill covers retrieval and management of these secondary ticket entities.
use `autotask-tickets`.
charges are separate billing paths; use `autotask-time-entries`.
expense item, not a ticket charge; use `autotask-expenses`.
Tool: `autotask_get_ticket_note`
Parameters:
Returns the full note content including author, creation time, note type (internal/external), and HTML/text body.
Tool: `autotask_search_ticket_notes`
Key parameters:
Tool: `autotask_get_ticket_attachment`
Parameters:
Returns attachment metadata and base64-encoded file content.
Tool: `autotask_search_ticket_attachments`
Key parameters:
Tool: `autotask_get_ticket_charge`
Parameters:
Returns charge details including amount, description, billing status, and associated ticket.
Tool: `autotask_create_ticket_charge`
Key parameters:
Tool: `autotask_update_ticket_charge`
Parameters:
Tool: `autotask_delete_ticket_charge`
Parameters:
Use with care — deleted charges cannot be recovered.
Tool: `autotask_search_ticket_charges`
Key parameters:
1. Use `autotask_get_ticket_details` to get the core ticket 2. Use `autotask_search_ticket_notes` with `ticketId` to retrieve all notes 3. Use `autotask_search_ticket_attachments` with `ticketId` to list files 4. Use `autotask_search_ticket_charges` with `ticketId` to see charges
1. Verify the ticket exists with `autotask_get_ticket_details` 2. Call `autotask_create_ticket_charge` with ticket ID, name, amount 3. Confirm charge appears with `autotask_search_ticket_charges`
1. Use `autotask_search_ticket_notes` filtered by `ticketId` and `noteType` (external only) 2. Collect and format note bodies for the report
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…