Integrations

AI assistants (MCP)

Ask Claude, Cursor, VS Code or another AI assistant about your clients, devices, onboarding and patching through Enlist's built-in MCP server, with an API key.

Enlist has a built-in MCP server (Model Context Protocol), so an AI assistant can look things up for you: "which of Harbor Dental's PCs are missing patches?", "why isn't FRONTDESK-02 ready yet?", "tag every kiosk Mac". The assistant signs in with an API key, so it can do exactly what that key can do and nothing more. There is nothing to install on the Enlist side.

Make a key for the assistant #

Make a key as in API: getting started, and name it after the assistant, such as Claude on my laptop. Tick only what you want the assistant to see:

  • clients:read for clients and sites.
  • devices:read for devices, onboarding, patching, health alerts, tags, groups and standard checks.
  • devices:organize instead of devices:read if the assistant may also set a device's tags and patch ring.
  • blueprints:read, team:read and audit:read for blueprints, the team and the activity log.
The assistant acts as you

Everything it does is limited to your own access and the scopes you ticked. It can never run a script or install on a device, onboard, retire or move one, approve a patch, or see a password or recovery key. Changes it makes show in the activity log as your key, marked via: mcp.

Connect your assistant #

The server's address is your MSP's own address with /api/mcp after it. If you sign in at https://northwind.enlistit.app, it is https://northwind.enlistit.app/api/mcp. It uses MCP's Streamable HTTP transport and takes the key in the Authorization header.

Claude Code #

claude mcp add --transport http enlist https://northwind.enlistit.app/api/mcp \
  --header "Authorization: Bearer $ENLIST_API_KEY"

Cursor #

Add this to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "enlist": {
      "url": "https://northwind.enlistit.app/api/mcp",
      "headers": { "Authorization": "Bearer enl_…" }
    }
  }
}

VS Code #

Add this to .vscode/mcp.json (VS Code asks for the key the first time and keeps it):

{
  "inputs": [
    { "id": "enlist-key", "type": "promptString", "description": "Enlist API key", "password": true }
  ],
  "servers": {
    "enlist": {
      "type": "http",
      "url": "https://northwind.enlistit.app/api/mcp",
      "headers": { "Authorization": "Bearer ${input:enlist-key}" }
    }
  }
}

Claude Desktop #

Claude Desktop starts local servers, so it reaches Enlist through mcp-remote (it needs Node.js). In Settings → Developer → Edit Config, add:

{
  "mcpServers": {
    "enlist": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://northwind.enlistit.app/api/mcp",
               "--header", "Authorization:${AUTH_HEADER}"],
      "env": { "AUTH_HEADER": "Bearer enl_…" }
    }
  }
}

Claude.ai and ChatGPT connectors in the browser need a sign-in flow (OAuth) that Enlist doesn't offer yet.

What the assistant can do #

The assistant only sees the tools your key's scopes reach.

ToolScopeWhat it does
list_clients, list_sitesclients:readClients with their device counts, and a client's sites
list_devices, get_devicedevices:readFind devices by hostname, serial number or user, by client, tag or group; one device with its inventory
get_device_onboarding, get_onboarding_sessiondevices:readWhere an onboarding is and why a step failed
get_device_os_patchesdevices:readA device's OS updates: missing, approved, installed or failed
list_device_tags, list_device_groups, list_group_devicesdevices:readTags and groups and who is in them
list_health_alerts, get_health_summarydevices:readOffline, encryption, antivirus and disk space alerts
get_standard_checks_summarydevices:readWhich devices still match their blueprint
list_os_patches, get_os_patch_report, get_cve_report, list_patch_ringsdevices:readPatches devices need, patch compliance, open vulnerabilities and patch rings
list_blueprints, get_blueprintblueprints:readBlueprints and their steps
list_teamteam:readPeople and their roles
list_activityaudit:readThe activity log, newest first
set_device_tags, set_device_patch_ringdevices:organizeSet a device's tags, or put it in the test, pilot or everyone patch ring

Limits #

Each tool call counts as one API request toward the key's limits (see Limits). A very large answer asks the assistant to narrow it, for example to one client. Revoke the key in Settings → API keys and the assistant stops at once.

Last updated 2026-11-17. Something wrong or missing? Email [email protected].