Productivity

Jamf Pro (Client Credentials)

Connect Jamf Pro (Client Credentials) with OAuth. Agents call it through a scoped CybrLink session.

Connect stays on CybrLink. Signed-out visitors go to sign-in. Signed-in visitors open the connect host at connect.cybrlink.dev.

OAuthScoped proxy

Connect through OAuth

The client approves access on the provider's authorization screen. CybrLink stores the resulting credential through Nango and exposes only scoped, auditable agent access.

Jamf Pro (Client Credentials) connection guide
Connect in portal

Step 1

Open OAuth connect

Step 2

Approve provider access

Step 3

Create a scoped MCP/API key

Sample request

// 1. Mint a session token for the end user
const session = await link.connect.session({
  integrationKey: "jamf",
  userId: "u_42",
});

// 2. After the user completes OAuth, proxy a request
const res = await link.proxy("jamf", "u_42", {
  method: "GET",
  endpoint: "/api/v1/me",
});

More in this category

Typed agent tools

Typed MCP tool schemas are not published for Jamf Pro (Client Credentials) yet. Connecting still lets an agent call this integration through CybrLink's scoped proxy. This page does not list a tool count until those schemas exist.

Jamf Pro (Client Credentials) + SI (super intelligence) agents: common questions

How do I connect Jamf Pro (Client Credentials) to an SI agent?
Create a free CybrLink account, open the dashboard, and click Connect on Jamf Pro (Client Credentials). You authorize once with OAuth; CybrLink stores the credential in its token vault and your agent reaches Jamf Pro (Client Credentials) through the CybrLink MCP server or the agent proxy API. The credential itself is never placed in the model's context.
Does Jamf Pro (Client Credentials) work with Claude, GPT, and other MCP clients?
Yes. CybrLink exposes a remote MCP (Model Context Protocol) server, so any MCP-capable client or agent framework — including Claude, OpenAI-based agents, and custom agents — can call Jamf Pro (Client Credentials) once you've connected it. Non-MCP agents can use the authenticated HTTP proxy instead.
Is it safe to give an SI agent access to Jamf Pro (Client Credentials)?
CybrLink scopes every connection to the permissions you grant, keeps tokens out of the model, logs each call to an activity audit trail, and lets you revoke the Jamf Pro (Client Credentials) connection at any time from the dashboard.