ConnectWise Asio MCP server and AI skills

What it can do

• Devices & endpointsFind endpoints and read their detail — online state and last-seen, system info, live CPU/memory/disk, services, installed applications, patch state, and CVE exposure.12skills

  Reads device state only — no reboot, no patch approval or deployment, no service start or stop.

  • The endpoint inventory grouped by company and site — device names and the ids every other device question needs.
  • Full system information for one endpoint, rather than the trimmed list row.
  • Online, offline, and last-seen — for whole companies, whole sites, or a named batch of endpoints in one call.
  • Who is logged on to a machine now, who was last, and when it last booted.
  • Current CPU, memory, and disk pressure on one endpoint — needs the performance read scope, and comes back empty where no recent sample has landed.
  • The services and daemons on one machine, with a name filter for checking whether a specific one is there.
  • Every distinct service seen across the monitored fleet — the vocabulary before you go hunting for one.
  • Installed applications across a company, a site, or a single endpoint, filterable by name and version.
  • One endpoint's patches with their KBs and install state — requires the patching read scope on the credential, or the tenant is refused.
  • CVE exposure for a batch of endpoints, looked up in a single pass.
  • The VMware vCenter and ESXi hosts under monitoring; a tenant that monitors no VMware simply has none.
  • Translate between Asio's two id spaces, including public and private — how a lookup that came back empty gets retried correctly.
• PoliciesPolicies, packages, and policy groups — including the effective policy actually applied to any given endpoint.9skills

  Reads policy configuration only — it cannot edit a policy, assign a package, or change a group's criteria.

  • Every policy available to the partner, with category and subcategory filing.
  • One policy opened out to its settings — the configured values, domain by domain, not just the name.
  • Where a policy actually lands: the packages and groups carrying it.
  • The policy packages, including which one is default and which clients and sites each is assigned to.
  • One package and its assignments together — the definition and its reach in a single answer.
  • The policy-group hierarchy, with parents and children in evaluation order.
  • A single group's criteria, the device group behind it, and the policy attached.
  • What one endpoint is really running once everything above it resolves — with the override document when someone left one in place.
  • The categories and subcategories policies are organized under.
• AutomationAutomation tasks with their run history and per-endpoint results, plus the fusion and shell script catalogues.7skills

  Catalogue and results only — there is no execute path, so it cannot run, queue, or schedule a task or script.

  • Every automation task defined for the partner — the catalogue, not a run button.
  • Automation in aggregate: how many tasks exist and what state they're sitting in.
  • One task's run history — each execution and how it came out.
  • A single run broken out machine by machine — which endpoints it worked on and which it didn't.
  • The automation that has touched one machine, as its own Automation tab shows it.
  • The fusion script catalogue from the Script Editor — what exists, read only.
  • The shell scripts on the shelf, listed the same way.
• Companies & sitesCompanies and the sites beneath them — the shape of who you manage.5skills
  • The client list as Asio holds it — every company under your partner account.
  • One company's record in full.
  • The sites under a single company — that client's offices and locations.
  • Every site across every client at once, for when the question is about locations rather than companies.
  • A single site's detail record.
• TicketingSearch service tickets, read their detail and notes, count them, and pull boards, statuses, and priorities.5skills

  Read-only — the create, update, and note-writing endpoints are unreachable, so nothing here can open, change, or close a ticket.

  • Search the service queue by status, priority, or company, with the matching total alongside.
  • One ticket's complete record.
  • The notes written on a ticket — the conversation behind the status.
  • The queue by the numbers for the partner as a whole.
  • Boards, statuses, priorities, types, and sources in one call — the vocabulary the queue is described in.
• Device groupsDevice groups, their endpoint membership, and which groups a given endpoint belongs to.3skills
  • Every device group, and whether it is static, predefined, or dynamic.
  • The endpoints inside one group — worth knowing a group can span more than one company.
  • The reverse lookup: which groups a given endpoint has ended up in.
• Alert suspensionsAlert-suspension rules — what's silenced, where, and until when.2skills

  Reads the rules only — it cannot create, extend, or lift a suspension, or silence an alert itself.

  • Every alert-suspension rule, and whether it is still active or has expired.
  • One rule in detail — what it silences, across which clients, sites, endpoints, or groups, and on what schedule.
• Identity & limitsWho the session is signed in as, the rate limits it works under, and what this host itself supports — the boundary of what this connection can be asked for.3skills
  • What your own host says it supports — and, where it says nothing about itself, a plain account of that rather than a guess dressed up as an answer.
  • The token's live rate-limit state — the number to check before a fleet-wide sweep, since the published limits contradict each other.
  • Which Asio identity this connection uses, the scopes it holds, and whether its token is still good.
• Custom fields5skills
  • All custom-field definitions for the partner (vendor-provided + partner-defined): id, entityType (client|site|endpoint|contact|ticket|ticketnote), name, attributeType, validationOptions, defaultValue.
  • One custom-field definition schema by id.
  • Custom-field VALUES set on one company (PUBLIC company id).
  • Custom-field VALUES set on one site (PUBLIC site id).
  • Custom-field VALUES set on one endpoint (PRIVATE endpoint id).
• Devices v16skills
  • All devices for the partner (v1, PUBLIC ids) — the whole-fleet device list with no company/site grouping call required first.
  • Company endpoints v1.
  • Site endpoints v1.
  • Details of one device by PUBLIC endpoint id (incl. rolesFeatures) — no v2 company/site scoping trio required.
  • Logged-on users + last-seen timestamps for one device by PUBLIC endpoint id.
  • Hypervisor guests.
• Fleet more1skills
  • Get company site.
• Mapping1skills
  • Fetch records that match given source attributes against one or more schemas (e.g. resolve a service-board name to its priority/severity mapping). all=true returns every matching record instead of just the first.
• Rollups2skills
  • Partner-level ops rollup in one call: active alert-suspension rules (named), ticket counts, and which rate-limit resource families are close to exhausted. Start here before a status check that would otherwise be three separate calls.
  • Fleet patch compliance rollup.
• Ticketing more5skills
  • All ticket categories (ticket family) for the partner.
  • All ticket tags available to the partner.
  • One ticket tag by id.
  • Service board teams.
  • Get ticket note.
• Topology5skills
  • List integration clients.
  • List sites for a client via the Asio Integration API — returns siteId/siteName.
  • List endpoints for a client+site via the Asio Integration API — returns endpointID/endpointType.
  • Integration endpoint details.
  • This vendor integration's registered product-status JSON schema (draft-07) — what a status push must conform to. Read-only lookup; this agent never pushes status.

How it has been taught to work it

Playbooks are the vetted techniques a session loads for this platform — what to check, in what order, and what a number means before it is reported.

• Asio Integration API — topology + full asset dump (a third id space)Need the fullest per-endpoint asset dump this agent can get (installed software, drives, network, users, shares, licenses), or need to explore via the Integration API's own client/site/endpoint hierarchy, or need this vendor integration's product-status schema.
  Vetted Sep 2, 2026
• Axcient ↔ Asio — RMM-managed endpoints with no backupWhich of our RMM-managed endpoints have no backup — backup coverage gaps, unprotected endpoints, "is this managed machine actually protected", per-client or fleet-wide coverage reconciliation.
  Vetted Aug 14, 2026
• ConnectWise RMM (Asio) domain model (what the application IS)Always when Asio is attached. Its domain model, and why it is not Automate.
  Vetted Aug 4, 2026Always on
• Querying ConnectWise RMM (Asio) — resource types, ids, gotchasAlways when Asio is attached. The live-verified call rules and where the docs lie.
  Vetted Aug 4, 2026Always on
• RMM (Asio) ↔ PSA — same clients, machines as configurationsA question spans ConnectWise RMM (Asio) and PSA for the same client — "which machines at the client with the most open tickets are offline", "is this ticketed machine patched", joining a device to its CI/ticket/agreement.
  Vetted Aug 4, 2026
• RMM automation history — tasks, instances, results (read-only)What automation ran, did a task succeed, per-endpoint automation results, what scripts exist. Never to RUN anything.
  Vetted Aug 4, 2026
• RMM custom fields — definitions and values (company/site/endpoint)What custom fields exist for the partner, what type/validation a field has, or what value is set for a specific company/site/endpoint.
  Vetted Sep 2, 2026
• RMM device inventory — endpoints, apps, servicesWhat devices does a client have, what software or services are on them, hardware/system details for an endpoint.
  Vetted Aug 4, 2026
• RMM fleet health — online/offline, stale, last-seenIs an Asio-managed machine or fleet healthy; what is offline, what has gone quiet, last-seen and last-boot on a client's endpoints.
  Vetted Aug 4, 2026
• RMM ops rollups — partner snapshot, fleet patch/CVE rollup, generic mapping lookupA quick partner-wide status check before a bigger investigation, a combined patch+CVE view across a set of endpoints, or a generic criteria-based lookup against an Asio mapping schema.
  Vetted Sep 2, 2026
• RMM patch posture — compliance, missing patches, reboot statePatch status/compliance for an endpoint or fleet, missing/critical patches, reboot pending, KB-level detail on an Asio-managed device.
  Vetted Aug 4, 2026
• RMM policy audit — policies, packages, effective policy, suspensionsWhat policies exist, what a policy contains, what applies to an endpoint, which alert suspensions are active.
  Vetted Aug 4, 2026
• RMM ticket review — search, notes, open vs closedRMM tickets — what is open, ticket detail and notes, counts by category, which statuses count as open.
  Vetted Aug 4, 2026

Plus 18 more every session carries regardless of platform — how to shape an investigation, keep every number traceable, and say plainly when something is broken.