--- title: "N-able N-central MCP server for AI agents - actionlake" description: "Give Claude 66 N-able N-central actions through one MCP server: customers, scheduled tasks. Your agent never holds the credential. 100,000 calls a month free." canonical: https://actionlake.com/connectors/n-able-n-central updated: 2026-10-22 --- Connectors · MSP & PSA # N-able N-central MCP server for AI agents. actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to N-able N-central and the rest of your systems. It gives your agent 66 N-able N-central actions (52 reads, 13 writes and 1 that wait for a confirmation) and holds the N-able N-central credential itself, so the agent never does. It paces N-able N-central's limits and records every call. [Connect N-able N-central free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing) 100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you. `claude mcp add --transport http actionlake https://connect.actionlake.com/mcp` the first call ``` do { action: "n_able_n_central.customers.list", intent: "check which N-able N-central account is connected" } # Retrieve a list of all customers. · read · 1 upstream call ``` - 66 actions in one signed file - 52 read look, never change - 13 write create and update - 1 wait for a yes destructive, confirmed first Set up ## Connect N-able N-central in three steps. 1. 01 ### Add actionlake to Claude. Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us. `https://connect.actionlake.com/mcp` 2. 02 ### Connect N-able N-central. Session login. actionlake opens the session and renews it when it expires. actionlake stores what you paste write-only, sealed under your tenant's key. - `user_api_token` N-central User-API Token (JWT) - `host` Where your N-able N-central lives: your host ``` account { op: "connections.requirements", service: "n_able_n_central" } # free: exactly what to paste, and what is found for you ``` 3. 03 ### Make the first call. Check before a write. Ask in plain words; Claude picks the action. Before anything changes, `check` validates the call and prices it, for free. ``` do { action: "n_able_n_central.customers.list" } # retrieve a list of all customers. · read · 1 upstream call check { action: "n_able_n_central.customers.create", input: { … } } # free: inputs, permissions, cost and confirmations, nothing sent ``` N-able N-central at a glance **Sign-in** Session login. actionlake opens the session and renews it when it expires. **You provide** `user_api_token` **Setup fields** `host` **Limits we pace to** 10 calls a second, per connection **API covered** N-central REST API (1.0), at your N-able N-central instance's API base URL, which you enter when connecting **Built from** N-able N-central's documentation, read 22 October 2026[developer.n-able.com](https://developer.n-able.com/n-central/reference) [developer.n-able.com](https://developer.n-able.com/n-central/docs/rest-api-known-issues-and-limitations) **Service file** Version 1.0.0, signed (Ed25519) **Cached reads** 49 of 52 reads, for up to 5 minutes; a write clears what it affects **Shared entities** 6, so ask can line N-able N-central up with your other systems **Data** Processed and stored in Sydney, Australia. No US region yet Capabilities ## What an AI agent can do in N-able N-central. 66 actions in 39 areas. Every one carries its effect, so a key can allow the reads and hold the rest. - **52** read look, never change - **13** write create and update - **1** destructive wait for a confirmation 1. ### Customers 4 3 read · 1 write · 0 destructive Retrieve a list of all customers. · PREVIEW: Creates a customer. · PREVIEW: Retrieve a customer. · PREVIEW: Retrieve a customer registration token. 2. ### Scheduled tasks 4 3 read · 1 write · 0 destructive Create a direct-support schedule task. · Retrieves detailed status per device for a given task. · Retrieves general information for a given task. · Retrieves aggregated status for a given task. 3. ### Sites 4 3 read · 1 write · 0 destructive Retrieve a list of all sites. · PREVIEW: Creates a site. · PREVIEW: Retrieve a site. · PREVIEW: Retrieve a site registration token. 4. ### Access groups 3 2 read · 1 write · 0 destructive PREVIEW: Creates a new organization unit type access group. · PREVIEW: Retrieve Access Groups Information for an Org Unit by ID. · PREVIEW: Retrieve detailed information for a specific Access Group by ID. 5. ### Device custom properties 3 2 read · 1 write · 0 destructive PREVIEW: Retrieve Device Custom Properties by device id · PREVIEW: Get the device custom property. · PREVIEW: Modify Device Custom Property 6. ### Device lifecycle info 3 1 read · 2 write · 0 destructive Retrieve a device asset lifecycle information by Device ID. · Modifies the Asset Lifecycle Information by Device Id. · Modifies the Asset Lifecycle Information by Device Id. 7. ### Org unit custom properties 3 2 read · 1 write · 0 destructive PREVIEW: Get the list of organization custom properties. · PREVIEW: Get the organization unit custom property. · PREVIEW: Update the organization unit custom property. 8. ### Org units 3 3 read · 0 write · 0 destructive Retrieve a list of all organization units. · PREVIEW: Retrieve an organization unit. · PREVIEW: Retrieve an organization unit registration token. **31 more areas · 39 actions** - Service orgs **3** - User roles **3** - Devices **2** - Maintenance windows **2** - Org custom property defaults **2** - Server info **2** - Access group links **1** - Active issues **1** - API root **1** - Appliance tasks **1** - Auth **1** - Auth links **1** - Custom PSA links **1** - Custom PSA ticket links **1** - Customer sites **1** - Device access groups **1** - Device assets **1** - Device custom property defaults **1** - Device filters **1** - Device maintenance windows **1** - Device scheduled tasks **1** - Device service monitor status **1** - Health **1** - Job statuses **1** - Org unit children **1** - Org unit devices **1** - Scheduled task links **1** - Service org customers **1** - Standard PSA links **1** - User links **1** - Users **1** Top actions ## The N-able N-central API, shaped for agents. The ids your agent types, what each does, and the one name it shares with other systems. 13 of N-able N-central's 13 action names are shared with at least one other connector, so an agent learns them once. | Action | What it does | Effect | Same name in | | --- | --- | --- | --- | | `n_able_n_central.customers.list` Retrieve a list of all customers. | Retrieve a list of all customers. | read | `crm.company.list` 162 connectors | | `n_able_n_central.users.list` PREVIEW: Retrieve the list of users. | PREVIEW: Retrieve the list of users. | read | `identity.user.list` 474 connectors | | `n_able_n_central.sites.list` Retrieve a list of all sites. | Retrieve a list of all sites. | read | `crm.location.list` 48 connectors | | `n_able_n_central.user_roles.list` PREVIEW: Retrieve a list of user roles for a given organization unit. | PREVIEW: Retrieve a list of user roles for a given organization unit. | read | `identity.role.list` 184 connectors | | `n_able_n_central.customers.create` PREVIEW: Creates a customer. | PREVIEW: Creates a customer. | write | `crm.company.create` 142 connectors | | `n_able_n_central.sites.create` PREVIEW: Creates a site. | PREVIEW: Creates a site. | write | `crm.location.create` 41 connectors | | `n_able_n_central.user_roles.create` PREVIEW: Add a new user role for a given organization unit. | PREVIEW: Add a new user role for a given organization unit. | write | `identity.role.create` 105 connectors | | `n_able_n_central.devices.list` Retrieve the list of devices. | Retrieve the list of devices. | read | `device.endpoint.list` 65 connectors | | `n_able_n_central.active_issues.list` PREVIEW: Fetch active issues | PREVIEW: Fetch active issues. | read | `monitoring.alert.list` 51 connectors | | `n_able_n_central.devices.get` Retrieve a device by ID. | Retrieve a device by ID. | read | `device.endpoint.get` 57 connectors | | `n_able_n_central.org_units.list` Retrieve a list of all organization units. | Retrieve a list of all organization units. | read | this connector | | `n_able_n_central.maintenance_windows.delete` PREVIEW : Deletes device patch maintenance windows by given list of Schedule Ids. | PREVIEW : Deletes device patch maintenance windows by given list of Schedule Ids. | destructive | this connector | Try it ## Prompts to paste into Claude. Each one names the N-able N-central actions it will call, so you know what it reads and what it changes before you send it. 1. Read read Which N-able N-central alerts are open right now? Group them by service. calls `n_able_n_central.active_issues.list` 2. Write write PREVIEW: Creates a customer in N-able N-central. Show me exactly what you will send before you save it. calls `n_able_n_central.customers.create` 3. Across systems read Which N-able N-central companies have invoices in NetSuite, and how many each? calls `n_able_n_central.customers.list` `netsuite.views.invoices` Across your systems ## N-able N-central, joined to the rest of your business. One `ask` fetches from N-able N-central and another system, joins the rows on the same customer on our side, and hands your agent the answer, not every row. - Which N-able N-central companies have invoices in NetSuite, and how many each? `n_able_n_central.customers.list` + `netsuite.views.invoices`, on `crm.company` · [NetSuite](https://actionlake.com/connectors/netsuite) - Which N-able N-central companies have tickets in HubSpot CRM, and how many each? `n_able_n_central.customers.list` + `hubspot_crm.tickets.list`, on `crm.company` · [HubSpot CRM](https://actionlake.com/connectors/hubspot-crm) Also mapped by other connectors `identity.user` **517** `crm.company` **227** `identity.role` **107** `device.endpoint` **69** `monitoring.alert` **56** `crm.location` **49** ask ``` ask { intent: "which N-able N-central companies have invoices in NetSuite, and how many each", steps: [ { action: "n_able_n_central.customers.list", as: "co", input: {}, limit: 100, max_pages: 5 }, { action: "netsuite.views.invoices", as: "inv", input: {}, limit: 100, max_pages: 5 }, { join: { left: "co", right: "inv", on: "crm.company", group_by: "co.name", select: ["co.name", "count(inv.id) as invoices"] } } ] } ``` Example. Run it through check first: it validates the steps and prices them, and it is free. Governance for N-able N-central ## Destructive actions wait for a yes. 1 N-able N-central action is destructive. This is it: - PREVIEW : Deletes device patch maintenance windows by given list of Schedule Ids. `n_able_n_central.maintenance_windows.delete` A destructive action runs only with `confirm: true`. Under the `human` policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after. do n_able_n_central.maintenance_windows.delete confirm_policy: **human** PREVIEW : Deletes device patch maintenance windows by given list of Schedule Ids.? **intent:** the user asked me to pREVIEW : Deletes device patch maintenance windows by given list of Schedule Ids. run suspended · waiting for a named person · key _n-able-n-central-agent_ cannot confirm itself In the console, or from an emailed signed link. a key for this connector ``` account { op: "keys.create", name: "n-able-n-central-agent", allowed_actions: ["n_able_n_central.*"], cap_calls: 2000, confirm_policy: "human_for_writes", approval_rules: [ { match: "n_able_n_central.maintenance_windows.delete", approver: "lead@example.com" } ] } ``` Illustrative. Scoped to N-able N-central only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person. Cost ## What N-able N-central costs on actionlake. Every N-able N-central action is one upstream call, the only thing actionlake bills. Searching, `check`, `cost`, `account` and any call N-able N-central refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000. - 1 upstream call per action all 66 N-able N-central actions - 66 actions page each page of a long list is one call - 49 reads can be cached a cache hit costs nothing - 100,000 calls a month, free paid plans from US$49 a month for 250,000 [See pricing](https://actionlake.com/pricing) Action index ## Every N-able N-central action. 66 actions by area: the id your agent calls, what it does, and its effect. **Customers 4** - `n_able_n_central.customers.create` PREVIEW: Creates a customer. write - `n_able_n_central.customers.get` PREVIEW: Retrieve a customer. read - `n_able_n_central.customers.get_registration_token` PREVIEW: Retrieve a customer registration token. read - `n_able_n_central.customers.list` Retrieve a list of all customers. read **Scheduled tasks 4** - `n_able_n_central.scheduled_tasks.create_direct` Create a direct-support schedule task. write - `n_able_n_central.scheduled_tasks.get` Retrieves general information for a given task. read - `n_able_n_central.scheduled_tasks.get_status` Retrieves aggregated status for a given task. read - `n_able_n_central.scheduled_tasks.list_status_details` Retrieves detailed status per device for a given task. read **Sites 4** - `n_able_n_central.sites.create` PREVIEW: Creates a site. write - `n_able_n_central.sites.get` PREVIEW: Retrieve a site. read - `n_able_n_central.sites.get_registration_token` PREVIEW: Retrieve a site registration token. read - `n_able_n_central.sites.list` Retrieve a list of all sites. read **Access groups 3** - `n_able_n_central.access_groups.create` PREVIEW: Creates a new organization unit type access group. write - `n_able_n_central.access_groups.get` PREVIEW: Retrieve detailed information for a specific Access Group by ID. read - `n_able_n_central.access_groups.list` PREVIEW: Retrieve Access Groups Information for an Org Unit by ID. read **Device custom properties 3** - `n_able_n_central.device_custom_properties.get` PREVIEW: Get the device custom property. read - `n_able_n_central.device_custom_properties.list` PREVIEW: Retrieve Device Custom Properties by device id read - `n_able_n_central.device_custom_properties.update` PREVIEW: Modify Device Custom Property write **Device lifecycle info 3** - `n_able_n_central.device_lifecycle_info.get` Retrieve a device asset lifecycle information by Device ID. read - `n_able_n_central.device_lifecycle_info.replace` Modifies the Asset Lifecycle Information by Device Id. write - `n_able_n_central.device_lifecycle_info.update` Modifies the Asset Lifecycle Information by Device Id. write **Org unit custom properties 3** - `n_able_n_central.org_unit_custom_properties.get` PREVIEW: Get the organization unit custom property. read - `n_able_n_central.org_unit_custom_properties.list` PREVIEW: Get the list of organization custom properties. read - `n_able_n_central.org_unit_custom_properties.update` PREVIEW: Update the organization unit custom property. write **Org units 3** - `n_able_n_central.org_units.get` PREVIEW: Retrieve an organization unit. read - `n_able_n_central.org_units.get_registration_token` PREVIEW: Retrieve an organization unit registration token. read - `n_able_n_central.org_units.list` Retrieve a list of all organization units. read **Service orgs 3** - `n_able_n_central.service_orgs.create` PREVIEW: Creates a new service organization (SO). write - `n_able_n_central.service_orgs.get` PREVIEW: Retrieve a service organization. read - `n_able_n_central.service_orgs.list` Retrieve a list of all service organizations. read **User roles 3** - `n_able_n_central.user_roles.create` PREVIEW: Add a new user role for a given organization unit. write - `n_able_n_central.user_roles.get` PREVIEW: Retrieve a user role for a given organization unit and user role id. read - `n_able_n_central.user_roles.list` PREVIEW: Retrieve a list of user roles for a given organization unit. read **Devices 2** - `n_able_n_central.devices.get` Retrieve a device by ID. read - `n_able_n_central.devices.list` Retrieve the list of devices. read **Maintenance windows 2** - `n_able_n_central.maintenance_windows.create` PREVIEW : Adds set of maintenance windows for a list of given devices. write - `n_able_n_central.maintenance_windows.delete` PREVIEW : Deletes device patch maintenance windows by given list of Schedule Ids. destructive **Org custom property defaults 2** - `n_able_n_central.org_custom_property_defaults.get` PREVIEW: Get the organization unit custom property. read - `n_able_n_central.org_custom_property_defaults.update` PREVIEW: Update the default organization unit custom property. write **Server info 2** - `n_able_n_central.server_info.get` Return version information of the running API-Service. read - `n_able_n_central.server_info.get_extra` PREVIEW: Get information about the version of different systems in N-central. read **Access group links 1** - `n_able_n_central.access_group_links.get` PREVIEW: List the access group related links. read **Active issues 1** - `n_able_n_central.active_issues.list` PREVIEW: Fetch active issues read **API root 1** - `n_able_n_central.api_root.get` List links to other endpoints. read **Appliance tasks 1** - `n_able_n_central.appliance_tasks.get` PREVIEW : Retrieves the appliance-task information. read **Auth 1** - `n_able_n_central.auth.validate` Check the validity of the API-Access token. read **Auth links 1** - `n_able_n_central.auth_links.get` List the authentication-related links. read **Custom PSA links 1** - `n_able_n_central.custom_psa_links.get` PREVIEW: List the custom psa related links. read **Custom PSA ticket links 1** - `n_able_n_central.custom_psa_ticket_links.get` PREVIEW: List the custom psa tickets related links. read **Customer sites 1** - `n_able_n_central.customer_sites.list` PREVIEW: Retrieve a list of sites under a customer. read **Device access groups 1** - `n_able_n_central.device_access_groups.create` PREVIEW: Creates a new device type access group. write **Device assets 1** - `n_able_n_central.device_assets.get` Retrieve Asset Information for a device by ID. read **Device custom property defaults 1** - `n_able_n_central.device_custom_property_defaults.get` PREVIEW: Retrieve Device Default Custom Property information by organization unit id and property id read **Device filters 1** - `n_able_n_central.device_filters.list` PREVIEW: Retrieve the list of filters. read **Device maintenance windows 1** - `n_able_n_central.device_maintenance_windows.list` PREVIEW : Retrieves all maintenance windows for a device. read **Device scheduled tasks 1** - `n_able_n_central.device_scheduled_tasks.list` Retrieve tasks for a specific device. read **Device service monitor status 1** - `n_able_n_central.device_service_monitor_status.list` PREVIEW : Retrieves the status of the service monitoring tasks for a given device. read **Health 1** - `n_able_n_central.health.get` Return the start and current time of the server. This indicates that the server is running. read **Job statuses 1** - `n_able_n_central.job_statuses.list` PREVIEW: Fetch job statuses read **Org unit children 1** - `n_able_n_central.org_unit_children.list` PREVIEW: Retrieve a list of all organization units children. read **Org unit devices 1** - `n_able_n_central.org_unit_devices.list` PREVIEW : Retrieve the list of devices by org unit id. read **Scheduled task links 1** - `n_able_n_central.scheduled_task_links.get` List the task-related links. read **Service org customers 1** - `n_able_n_central.service_org_customers.list` PREVIEW: Retrieve a list of all customers under a service organization. read **Standard PSA links 1** - `n_able_n_central.standard_psa_links.get` PREVIEW: List the standard psa related links. read **User links 1** - `n_able_n_central.user_links.get` PREVIEW: List the user related links. read **Users 1** - `n_able_n_central.users.list` PREVIEW: Retrieve the list of users. read Questions ## The N-able N-central MCP server, answered. **Is there a N-able N-central MCP server for Claude?** Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 66 N-able N-central actions across customers, scheduled tasks, sites and access groups, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by N-able N-central. **What do I need to connect N-able N-central?** N-central User-API Token (JWT). Plus your host. The free call account { op: "connections.requirements", service: "n_able_n_central" } lists exactly what to paste. **Can an AI agent delete or change things in N-able N-central?** Only if its key allows it, and only with an explicit confirmation. 1 N-able N-central action is destructive, including PREVIEW : Deletes device patch maintenance windows by given list of Schedule Ids.. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it. **Will an AI agent use up my N-able N-central API limit?** actionlake paces every call to the limits in the N-able N-central service file: 10 calls a second per connection. Repeated reads are answered from cache (49 N-able N-central actions can be), which never reaches N-able N-central. **What does a N-able N-central action cost?** One upstream call, the only unit actionlake bills. A list that pages bills one call per page (66 N-able N-central actions page). Cache hits, searches, dry runs and calls N-able N-central refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000. **Which N-able N-central API does it cover?** The N-central REST API (1.0) at your N-able N-central instance's API base URL, which you enter when connecting. It is built from N-able N-central's documentation as read on 22 October 2026. 66 actions in 39 areas, each one in the signed service file (version 1.0.0). **Can I combine N-able N-central with my other systems?** Yes. ask joins N-able N-central to NetSuite or HubSpot CRM on the same customer and returns the answer rather than every row. N-able N-central maps crm.company, which 227 other connectors also map. **Does actionlake keep my N-able N-central data, and where?** actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to 5 minutes, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your N-able N-central credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models. **Which AI clients can use it?** Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names. ## More connectors like N-able N-central Shares the most action names with - [TP-Link Omada Open API 11](https://actionlake.com/connectors/tp-link-omada-open-api) - [Veeam Service Provider Console 10](https://actionlake.com/connectors/veeam-service-provider-console) - [Kaseya VSA 10](https://actionlake.com/connectors/kaseya-vsa) - [Datto RMM 7](https://actionlake.com/connectors/datto-rmm) - [Action1 7](https://actionlake.com/connectors/action1) - [Axcient x360Recover 5](https://actionlake.com/connectors/axcient-x360recover) Joins with, on shared entities - [Palo Alto Networks Cortex XDR 4](https://actionlake.com/connectors/palo-alto-networks-cortex-xdr) - [Microsoft 365 Users 3](https://actionlake.com/connectors/microsoft-365-users) - [ServiceNow 3](https://actionlake.com/connectors/servicenow) - [Genesys Cloud CX 3](https://actionlake.com/connectors/genesys-cloud-cx) - [Zoho Books 3](https://actionlake.com/connectors/zoho-books) - [ERPNext (Frappe) 3](https://actionlake.com/connectors/erpnext-frappe) Browse - [All MSP & PSA connectors](https://actionlake.com/connectors/category/msp-and-psa) - [All connectors](https://actionlake.com/connectors) - [How actionlake compares](https://actionlake.com/compare) actionlake is independent. It is not made or endorsed by N-able N-central; the name is the vendor's own. Counts are from the N-able N-central service file, version 1.0.0. ## Give your agent N-able N-central today. [Connect N-able N-central free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing) Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free. --- Source: https://actionlake.com/connectors/n-able-n-central More: https://actionlake.com/llms.txt