Can AI agents automate Iru Endpoint Management?

Iru Endpoint Management, the product formerly branded Kandji, is automatable today through the tenant REST API and a first-party hosted MCP server. Keep the slug kandji. The opened API overview and the public OpenAPI document establish a JSON REST surface at https://{subdomain}.api.kandji.io and https://{subdomain}.api.eu.kandji.io, with GET, POST, PATCH, and DELETE, Bearer-token authentication, and a 10,000-request-per-hour tenant rate limit. Documented resources include devices and device actions, Blueprints, Library items, ADE tokens, Prism, users, tags, threats, vulnerabilities, settings, and audit events. Tokens are created in Access; permissions are scoped per token. API access may need a Customer Success Manager to enable it on the tenant. The opened Iru MCP guide is a real server contract, not homepage marketing: the tenant URL is https://YOUR_TENANT.connect.iru.com/mcp-server/connector/kandji/tools, authenticated with X-API-Key and X-MCP-Profile, and it exposes the same Enterprise API as MCP tools for Cursor, Claude Desktop, and Codex. MCP calls share the REST rate limit. This record is not Jamf and not Microsoft Intune. Connector catalogs were not opened. An official tenant SDK or tenant CLI was not established. Computer-use viability is unassessed. API scores 8 and is the best path. MCP scores 7 because the official server is useful and permission-scoped rather than unusually complete.

Best path today: api · Overall automatability: 8/10