Connect to N-able MCP in 2 Simple Steps

N-able MCP lets you connect such AI tools as Claude, GitHub Copilot, Gemini and many more - directly to your N-able environment. Built on the N-able GraphQL API, it gives AI assistants real-time access to N-central device data, N-sight RMM data, and more via the N-able GraphQL API.

Ask questions in natural language, run compliance checks, and query your fleet without writing code or navigating separate product APIs.

View the full list of default and custom tools currently available.

1. Choose your endpoint

N-able MCP provides three distinct endpoints for different purposes. Choose the endpoint that matches your use case before configuring your AI tool or IDE.

If you open the MCP endpoint in a web browser you may see an RBAC: access denied message. This is expected because N-able MCP only accepts POST requests.

2. Connect your AI Tool or IDE (Non-Exhaustive Examples)

Before you start: Get your API Token

To connect N-able MCP to an AI tool or IDE, you need a valid API token. Tokens are tied to the N-able SSO user account that creates them, so the token only returns data that account has permission to see.

To communicate with N-able MCP, clients must provide a valid authorization token via the HTTP header:

Authorization: Bearer <YOUR_API_TOKEN>

Permissions

API tokens inherit permissions from the N-able SSO user who created them, so authorization depends on that user account's access.

If a token does not have adequate permissions:

• Queries may fail with a 401 Unauthorized error
• Fields your user account cannot access may return null rather than an error
• Device lists will only include customers your account has permission to see

Example: if your token was created by a user with access to 3 of your 10 customer accounts, a query for all devices will only return devices from those 3 accounts.

N-able MCP works with any MCP-compatible AI tool or IDE. Find your tool below, copy the configuration, and restart the application. If your tool is not listed, the same pattern applies: use the server URL and pass your API token in the Authorization header.

Pick your tool

{
"mcpServers": {
  "n-able": {
    "command": "npx",
    "args": [
      "-y",
      "mcp-remote",
      "https://api.n-able.com/mcp/mcp-read-only",
      "--header",
      "Authorization: Bearer <YOUR_API_TOKEN>"
  			]
  	}
  }
}

{
  "mcpServers": {
    "n-able": {
      "type": "http",
      "url": "https://api.n-able.com/mcp/mcp-read-only",
      "headers": {
        "Authorization": "Bearer <YOUR_API_TOKEN>"
      }
    }
  }
}

{
  "mcpServers": {
    "n-able": {
      "httpUrl": "https://api.n-able.com/mcp/mcp-read-only",
      "headers": {
        "Authorization": "Bearer <YOUR_API_TOKEN>"
      }
    }
  }
}

{
  "servers": {
    "n-able": {
    	"url": "https://api.n-able.com/mcp/mcp-read-only",
    	"type": "http",
    	"headers": {
    		"Authorization": "Bearer <YOUR_API_TOKEN>"
    	}
    }
  },
  "inputs": []
}

5. Verify it's working (Expected Behavior)

Once N-able MCP is configured properly:

✔️ There should be no console errors

• No connection failures
• No token-related errors
• N-able MCP tools visible to the agent

✔ N-able MCP server visible to the agent ✔ Requests authenticated using an API token ✔ Agent can resolve the schema and execute queries

Step 1: Quick connection check

After verification, you can test the connection by asking:

"You are currently managing 42 devices across all your customers."

# Query may differ between AI models

query GetAssetCount {
  assetSearch(first: 1) {
    totalCount
  }
}

{
  "data": {
    "assetSearch": {
      "totalCount": 42
    }
  }
}

The agent should have used the default MCP tools to run a GraphQL operation and return an expected output like:

The number will reflect the actual device count in your tenant.

This proves that:

• Authentication is correct
• Default tools are available
• The N-able GraphQL API is reachable

Step 2: Real MSP example

After the quick connection check, try a query that demonstrates an operational use case for MSP automation:

  "You have 28 Windows devices without full BitLocker encryption across your customers. Acme Ltd has the most unprotected devices. Would you like me to list them all or break it down by customer?"

# Query may differ between AI models

query UnencryptedWindowsDevices {
  assetSearch(
    first: 50
    where: {
      bitlocker: { protectionStatus: { notEquals: FULL } }
      operatingSystem: { type: { equals: WINDOWS } }
    }
    orderBy: [{ field: CUSTOMER_NAME, direction: ASC }]
  ) {
    totalCount
    nodes {
      name
      bitlocker {
        protectionStatus
      }
      customer {
        name
      }
      operatingSystem {
        name
        version
      }
    }
  }
}

 {
  "data": {
    "assetSearch": {
      "totalCount": 28,
      "nodes": [
        {
          "name": "DESKTOP-04",
          "bitlocker": {
            "protectionStatus": "NONE"
          },
          "customer": {
            "name": "Acme Ltd"
          },
          "operatingSystem": {
            "name": "Microsoft Windows 11 Pro",
            "version": "10.0.22621"
          }
        },
        {
          "name": "LAPTOP-12",
          "bitlocker": {
            "protectionStatus": "PARTIAL"
          },
          "customer": {
            "name": "Acme Ltd"
          },
          "operatingSystem": {
            "name": "Microsoft Windows 11 Pro",
            "version": "10.0.22621"
          }
        }
      ]
    }
  }
}

Current tools

View the full list of default and custom tools currently available.

Error Handling & Troubleshooting

Additional References

• Apollo MCP Server - https://www.apollographql.com/docs/apollo-mcp-server
• N-able GraphQL API - schema changelog - https://studio.apollographql.com/public/N-able/variant/public/changelog
• CAT-MIP MCP Standard - https://cat-mip.org/ - External CAT-MIP project documentation related to MCP interoperability.
• CAT-MIP Releases - https://github.com/cat-mip/cat-mip/releases - Release history for the CAT-MIP project.

Share your feedback

N-able MCP is in active development and the tools added next will be shaped by what MSP automation workflows actually need. If something is missing, broken, or could work better, let us know.