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),…
HubSpot tasks, notes, and associations: task priority and status values, notes-vs-tasks semantics, the association type matrix linking contacts, companies, deals, and tickets, and engagement-history workflows.
$ npx -y skills add wyre-technology/msp-claude-plugins --skill activities --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/activitiesContext preview
The summary Claude sees to decide when to auto-load this skill.
HubSpot tasks, notes, and associations: task priority and status values, notes-vs-tasks semantics, the association type matrix linking contacts, companies, deals, and tickets, and engagement-history workflows.
name: "HubSpot Activities" description: > HubSpot tasks, notes, and associations: task priority and status values, notes-vs-tasks semantics, the association type matrix linking contacts, companies, deals, and tickets, and engagement-history workflows. when_to_use: >- When logging notes, creating follow-up tasks, or linking CRM objects together in HubSpot. Use when: hubspot task, hubspot note, hubspot activity, hubspot association, hubspot engagement, hubspot log, hubspot follow-up, hubspot link objects, hubspot relationship, activity management hubspot, or task creation hubspot.
Activities in HubSpot encompass tasks, notes, and other engagement records that track interactions with contacts, companies, deals, and tickets. Associations are the links that connect HubSpot CRM objects together -- a contact associated with a company, a deal associated with a contact, a note associated with a ticket. For MSPs, activities provide the service history and follow-up tracking that drives client satisfaction, while associations ensure that every interaction is visible from any related record.
pipeline and stage, not a task; use `hubspot-tickets`.
note, task, and association only; object fields live in `hubspot-contacts`, `hubspot-companies`, `hubspot-deals`, or `hubspot-tickets`.
the PSA is the system of record for those.
| Tool | Description | Key Parameters | |------|-------------|----------------| | `hubspot_create_task` | Create a task | `hs_task_subject` (required), `hs_task_body`, `hs_task_priority`, `hs_timestamp` | | `hubspot_create_note` | Create a note | `hs_note_body` (required), `hs_timestamp` |
| Tool | Description | Key Parameters | |------|-------------|----------------| | `hubspot_create_association` | Create an association between two objects | `fromObjectType`, `fromObjectId`, `toObjectType`, `toObjectId`, `associationType` | | `hubspot_access_associations` | List associations for an object | `objectType`, `objectId`, `toObjectType` |
| Tool | Description | Key Parameters | |------|-------------|----------------| | `hubspot_open_hubspot_ui` | Open HubSpot UI for an object | `objectType`, `objectId` | | `hubspot_get_user_details` | Get details of the current user | None |
Call `hubspot_create_task` to create a follow-up task:
**Example: Create a follow-up task:**
**Example: Create an onboarding task:**
Call `hubspot_create_note` to log an activity:
**Example: Log a meeting note:**
**Example: Log a support resolution:**
Call `hubspot_create_association` to link two CRM objects:
**Example: Associate a contact with a company:**
**Example: Associate a deal with a company:**
**Example: Associate a note with a contact:**
Call `hubspot_access_associations` to list all objects associated with a given object:
**Example: Get all contacts for a company:**
**Example: Get all deals for a contact:**
**Example: Get all tickets for a company:**
HubSpot supports associations between all major CRM object types:
| From | To | Association Type | Description | |------|----|-----------------|-------------| | contact | company | `contact_to_company` | Person works at organization | | deal | contact | `deal_to_contact` | Contact is involved in the deal | | deal | company | `deal_to_company` | Deal is for this company | | ticket | contact | `ticket_to_contact` | Contact reported the ticket | | ticket | company | `ticket_to_company` | Ticket is for this company | | note | contact | `note_to_contact` | Note is about this contact | | note | company | `note_to_company` | Note is about this company | | note | deal | `note_to_deal` | Note is about this deal | | note | ticket | `note_to_ticket` | Note is about this ticket | | task | contact | `task_to_contact` | Task i
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…