jamf

This Jamf Pro MCP Server provides a Code Mode workflow for interacting with Jamf Pro APIs. In Code Mode, you configure two MCP tools: jamf_search to discover API methods and jamf_execute to run JavaScript in a sandboxed VM that uses a typed Jamf API client. Use jamf_search to locate available endpoints and see method signatures, then craft code in jamf_execute to perform multi-step workflows across the Jamf Pro API. The sandboxed execution context enforces safety features such as plan/apply capability checks, concurrency throttling, and an explicit approval gate for high-impact actions. The result is a compact, token-efficient tool surface that can orchestrate complex tasks without exposing every API endpoint as a separate tool.

Prerequisites:

• Node.js v18 or later installed on the host
• npm or pnpm for package installation

Step-by-step:

1. Clone the repository: git clone https://github.com/dbankscard/jamf-mcp-server.git cd jamf-mcp-server

2. Install dependencies: npm install

3. Build the project (Code Mode is used by default in the Code Mode entry): npm run build

4. Start the server (as Code Mode in MCP config):

   • Ensure JAMF_URL, JAMF_CLIENT_ID, and JAMF_CLIENT_SECRET are configured in your environment or via your deployment system
   • Use the provided mcp_config snippet to register jamf-code with your MCP runtime
   • Run the MCP runtime to connect to the jamf-code server

5. Validate installation by invoking jamf_search and jamf_execute through your MCP client and confirming responses from Jamf Pro

Prerequisites summary:

• Node.js >= 18
• Access to a Jamf Pro instance with API credentials
• A hostable MCP runtime to load the jamf-code server definition

Tips and caveats:

• Use Code Mode to minimize the number of tool definitions; jamf_search and jamf_execute are used to discover and execute against the Jamf API.
• Configure JAMF_MAX_CONCURRENCY (default 5) to throttle API calls and reduce 429 errors.
• Use the plan/apply workflow for high-impact operations to preview changes before execution.
• Keep API credentials secure; rotate client secrets regularly and restrict permissions to only what is required.
• If you upgrade Jamf Pro API versions, revalidate the typings used by the Jamf SDK and update any breaking changes in jamf_execute code templates.