Learn about the Asset MCP

The Asset MCP connects N-zo directly to your live device data. Instead of asking about N-able products, you’re asking about your own devices, their specifications, current status, and logged-in users.

Asset Filter

Asset Filter is intended for asset and device-focused questions, such as identifying systems by configuration, status, or ownership. N-zo translates natural-language questions into GraphQL queries and returns matching assets.

Where data comes from

Example questions to ask N-zo

  • Show me all devices last rebooted on or before 10th Feb 2026

  • Which assets belong to customer Acme Corp?

  • Find devices with less than 8 GB of RAM.

  • Are there any devices with Joe Bloggs logged in right now?

  • Show me offline devices in the London site.

N-zo cannot always tell the time, so adding a date helps ensure accurate answers to time-based questions.

Returned asset data

Each matching asset returns a rich set of information, including identity, hardware, operating system, connectivity, and user information.

Field

Category

Description

id

Identity

Unique internal identifier for the asset

name

Identity

A unique identifier for the asset. You can update this in N-central or N-sight

description

Identity

Notes or comments associated with the device inN-central or N-sight

lastBootedAt

Activity

The last time the device was restarted

customer.name

Ownership

The name of the client that owns the asset

site.name

Ownership

The name of the client site where the device is located

serviceOrganization.name

Ownership

The name of the MSP or service organisation that manages the asset

operatingSystemInfo.name

OS

The name of the operating system

operatingSystemInfo.version

OS

The OS version, including bit version and build number

operatingSystemInfo.architecture

OS

The processor architecture (e.g. x86-64)

operatingSystemInfo.type

OS

The operating system type: Windows, macOS, or Linux

cpu.name

CPU

The brand and model of the processor (e.g. Intel Core i7-12700K, AMD Ryzen 9 7950X)

cpu.cores

CPU

The number of processing units within a CPU — more cores improve multitasking

cpu.type

CPU

The processor architecture or category (e.g. x86 32-bit, x86-64 64-bit)

systemInfo.hostname

Hardware

A human-readable name that identifies the device on a network

systemInfo.memoryTotalSizeBytes

Hardware

The total installed RAM on the device — N-zo displays this in GB for you

systemInfo.netBiosName

Hardware

A short name (up to 15 characters) used to identify a device on a local network

systemInfo.manufacturer

Hardware

The name of the asset manufacturer

systemInfo.model

Hardware

The model name or number of the device

systemInfo.serialNumber

Hardware

The device serial number

loggedInUsers.loginName

Users

The active user sessions on the device — useful for monitoring, security, and compliance

agentConnection.status

Status

Whether the agent is currently connected to cloud servers

agentConnection.statusChangedAt

Status

The timestamp of the last status change (e.g. Active to Inactive)

View detailed field descriptions

For detailed descriptions of each field, see the N-able User Guide: Data columns in the Assets view (N-central) or Data columns in the Assets view (N-sight).

Filter Options

Filter your assets using natural language. N-zo handles unit conversion and date parsing automatically. The following sections explain the available filters and how results are matched.

Filter Field

Type

Match Method

Notes / Example

Asset Name

Text

Contains

e.g. 'LAPTOP' matches 'ACME-LAPTOP-01'

Description

Text

Contains

Partial matches supported

Customer Name

Text

Contains

e.g. 'Acme' matches 'Acme Corp'

Site Name

Text

Contains

Partial site name supported

CPU Name

Text

Contains

e.g. 'i7' matches 'Intel Core i7-...'

CPU Type

Text

Contains

Partial match

Logged-In User

Text

Contains

Best with a full name, e.g. 'Joe Bloggs'

Agent Status

Text

Contains

e.g. 'online', 'offline'

Current filter behavior

Most filters use a contains match, and date and number filters use less than or equal to. As a result, some searches - for example “exactly 8 cores” or “booted after a specific date”- aren’t currently supported.

This is a known limitation, and we’re actively enhancing filter behavior. Please share feedback on the searches that are most valuable to you.

Result limits for asset queries

When running an asset filter query, N-zo can retrieve up to 10,000 matching devices from your estate. However, only the first 50 results are passed to the AI for analysis and display.

In practice, this means that broad queries may return only a subset of matching devices. To get more useful results, narrow your query with additional filters - such as customer, site, operating system, or status - to ensure the information you are looking is included in the first 50.

We’re working to improve this experience. If these limits affect your workflows, please share your feedback.

Asset Performance

Asset Performance supports reviewing the performance of a specific device. N-zo retrieves CPU and memory usage from the previous 24 hours and includes the device’s hardware details, providing a snapshot of recent activity and current specifications.

Where data comes from

Example questions to ask N-zo

  • How has DESKTOP-ACME01 been performing today?

  • Show me the CPU and memory usage for Joe's laptop over the last 24 hours.

  • What are the performance stats for the London file server?

Asset Permissions

Asset Permissions is used when you need to understand which actions you are authorized to perform on a specific device. This is useful for troubleshooting access issues or confirming permissions before attempting an action.

Where data comes from

Example questions to ask N-zo

  • What permissions do I have on DESKTOP-ACME01?

  • Can I manage the London server?

  • Check my access level for the Acme Corp devices.

 

How N-zo identifies the device for Asset Performance and Asset Permissions

Asset Performance and Asset Permissions both require an internal asset ID to retrieve device data or check permissions. If you reference a device by name or description, N-zo first uses Asset Filter to locate the matching device, then retrieves the relevant performance metrics or permissions. You may see this appear as two steps in the response, this is expected behaviour and not an error.