Jamf MCP server
Search Jamf developer docs, generate API code, and run Jamf API requests from your AI agents.
About
Connect Tracecat to Jamf's developer MCP server to find the right Jamf API call and draft integration code from AI agents working alongside Mac admins and SOC engineers. The server searches Jamf's OpenAPI specs, covering the Jamf Pro API, the Classic API, the Jamf Inventory API, and the Jamf Security APIs, and returns endpoint details with parameters and auth requirements. It does not manage devices in your Jamf Pro, Jamf Protect, or Jamf Security Cloud tenant. Use it to look up an endpoint, then run that call through execute-request with your own credentials or through a Tracecat HTTP action.
Setup
- 1
No credentials needed
Jamf's developer MCP server at `https://developer.jamf.com/mcp` needs no credentials. Tracecat connects to it directly. The `execute-request` tool sends whatever API request the agent builds, so any Jamf credentials it uses come from that request, not from the server.
- 2
Select the
Jamftile in the Tracecat MCP catalogOpen the
MCP catalogin your workspace, select theJamftile, and click Connect. - 3
Enable
Jamfin your agentIn your
ai.agentaction orAgents→toolstab, selectJamffrom theMCP integrationsdropdown.
Tools
list-specsList the OpenAPI specs the server knows, including the Jamf Pro API, Classic API, Jamf Inventory API, and Jamf Security APIs.
list-endpointsList every API path and HTTP method in a spec with a short summary.
search-endpointsSearch paths, operations, and parameters to find the endpoint for a task.
get-endpointReturn the details of one endpoint, including parameters, security schemes, and servers.
get-server-variablesReturn the server variables for each server in a spec, such as the instance URL.
execute-requestSend a caller-supplied HAR request to a Jamf API and return the response. The server flags it as destructive.