MCP Capabilities
Default tools and custom tooling
N-able MCP exposes the following default tools:
| Tool | What it does | When to use it | Permission required |
|---|---|---|---|
introspect | Shows every field and data type available for a given object in the N-able GraphQL API, such as an asset, customer, or policy. | Useful when exploring the API manually. If you are using an AI assistant, it runs this automatically so you do not have to. | Always on |
search | Searches the N-able GraphQL API to find what is queryable: fields, objects, and filters matching a keyword. | Useful when you are not sure what data exists. If you are using an AI assistant, it handles this step on your behalf. | Always on |
validate | Checks a query for errors before it runs. Confirms fields exist, syntax is correct, and the query will return a result. | Worth running before executing any query you have written manually. If you are using an AI assistant, it does this before every execution. | Always on |
execute | Runs a query against your fleet via the N-able GraphQL API and returns real data: device status, customer info, compliance state, and anything else in N-able platform. | This is what retrieves your data. Whether querying directly or through an AI assistant, all results come through here. | Must be enabled |
How default tools are used
When using N-able MCP with an AI assistant,
introspect, search, and validate run automatically in the background. You can also call them directly when exploring or building against the N-able GraphQL API. The only tool you need to explicitly enable in your MCP configuration is execute.During the preview period, N-able MCP will expand its toolset based on user feedback. The following additional tools are currently available, with more on the way:
| Tool | What it does | When to use it |
|---|---|---|
get_asset_inventory | Returns a paginated list of all devices under management across your customers. | Use this for fleet-wide inventory checks or when you need a full list of devices before filtering or reporting. |
get_single_asset_details_and_metrics | Returns detailed information and performance metrics for one specific device. Requires the device ID. | Use this when you need the full picture on a single device: OS version, health metrics, agent status, and more. |
assign_tags_to_assets | Applies one or more tags to a set of devices. | Use this to group or organize devices by customer, type, location, or any other category you manage across your N-able environment. |
list_script_tasks_for_asset | Returns all script tasks that have been run against a specific device, including their status and results. | Use this to check what scripts have been executed on a device and whether they completed successfully |
Discovering Available Tools
Available tools depend on your permission level and workspace configuration. Asking your AI assistant directly shows exactly what's enabled for your environment, right now.
You can ask your AI assistant or client directly, using natural language such as:
- "What tools and capabilities are available to me?"
- "What tools are available for me in N-able MCP?"
- "What tools are available for me in N-central MCP?"
- "What tools are available for me in N-sight MCP?"
Why query your endpoint directly?
- Real-time accuracy - reflects newly deployed tools and API changes as soon as they ship.
- Environment context - shows the tools, roles, and permissions configured for your active workspace, rather than a generic list.
- Exact schemas - lets your assistant inspect parameters, required inputs, and expected output formats directly.
Quiz Time
Ready for a quick challenge?
Take the N-able MCP Quiz to check your understanding and reinforce key concepts.
Updated about 2 months ago
Did this page help you?