Jamf Pro MCP

Jamf Pro + AI - for ChatGPT, Claude, GitHub Copilot, Microsoft 365 Copilot, Gemini, and any agent that speaks MCP

Unofficial. Community-built Claude Code Skill and MCP server for the Jamf

API. Not affiliated with, endorsed by, or sponsored by JAMF Software, LLC.

▶ Watch the 30-second demo - demo data is simulated; every command shown exists in the real CLI.

Every client's Jamf Pro in one CLI: register each instance once, then find devices, check posture and patch status, and audit policies across all of them. Works with the AI you already use - ChatGPT (Plus/Pro+), Claude Desktop, Codex, Claude Code, Claude Cowork, and GitHub Copilot - plus Microsoft 365 Copilot / Copilot Studio and Google Gemini via the remote path. Free, open source, runs on your laptop. Built for MSP owners. No code required.

Works with your agent

The six agents MSP owners actually use (self-serve, works today):

For ChatGPT, run jamf-pro-mcp --transport http with JAMF_PRO_MCP_HTTP_TOKEN set, on an HTTPS host; every request sends that token. See mcp-install.md.

Also for the Microsoft and Google stacks

Big install base, but an honest heads-up: these are the remote / enterprise path, not the local binary you just installed.

Skill-native agents (also covered): Hermes and OpenClaw read this skill's SKILL.md directly *and* speak MCP - see their install sections below. Also works with Cursor, Windsurf, Cline, Continue.dev, and Zed via MCP. Full per-tool wire-up: [docs/which-agent.md](../../docs/which-agent.md).

Run more than one agent? Install across all 51+ supported agents in one command: npx skills add Servosity/msp-skills@latest (requires Node.js, then run the per-skill installer for the CLI/MCP binaries). See docs/which-agent.md.

Install in 60 seconds

Fastest for Claude Desktop - one-click .mcpb

Download Jamf Pro MCP (.mcpb) - then open Claude Desktop > Settings > Extensions and select the file. One click, no JSON, no shell. (Browse every Jamf Pro release on the releases page.)

Prefer the Claude Code plugin? Add the marketplace once, then install - works immediately, no directory listing required:

/plugin marketplace add Servosity/msp-skills

/plugin install jamf-pro@msp-skills

Path A - paste one prompt into your AI agent (recommended)

Copy this into Claude Code, Codex CLI, or Claude Cowork:

Install the Jamf Pro Skill and MCP server from Servosity/msp-skills in this agent workspace. If this workspace uses a POSIX shell (macOS, Linux, WSL, or Bash), run bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/jamf-pro/install.sh). If it uses Windows PowerShell, run iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/jamf-pro/install.ps1 | iex. Then authenticate per the README and run jamf-pro-cli --help to explore.

The same prompt works in any agent that can run shell.

Path B - run the installer yourself

Windows (PowerShell):

iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/jamf-pro/install.ps1 | iex

macOS / Linux:

bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/jamf-pro/install.sh)

The installer drops both jamf-pro-cli (the CLI) and jamf-pro-mcp (the MCP server) into your user bin path. Claude Code, Codex, and Cowork discover the Skill via SKILL.md in this directory.

Verify:

jamf-pro-cli --version

Upgrade to the latest version

The installer always fetches the current release - re-run it to upgrade:

macOS / Linux:

bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/jamf-pro/install.sh)

Windows (PowerShell):

iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/jamf-pro/install.ps1 | iex

Claude Desktop .mcpb users: download the latest .mcpb (top of this section) and re-select it in Settings > Extensions. Claude Code plugin users: /plugin update jamf-pro@msp-skills.

Add to Claude Desktop, GitHub Copilot, Gemini CLI, Microsoft 365 Copilot, or another MCP client

After the installer runs, see [mcp-install.md](./mcp-install.md) and [docs/which-agent.md](../../docs/which-agent.md) for the per-agent wire-up - one section per agent, including the GitHub Copilot servers key and the remote Microsoft 365 Copilot / Copilot Studio path. Claude Desktop's Settings > Extensions panel is the simplest path; the MCP config block (for users who prefer editing JSON) is documented in mcp-install.md.

Install for Hermes

From the Hermes CLI:

hermes skills install servosity/msp-skills/skills/jamf-pro --force

Inside a Hermes chat session:

/skills install servosity/msp-skills/skills/jamf-pro --force

Hermes speaks MCP natively, so it can also use the jamf-pro-mcp server directly - same install path, same env vars.

Install for OpenClaw

Tell your OpenClaw agent (copy this):

Install the jamf-pro skill from https://github.com/servosity/msp-skills/tree/main/skills/jamf-pro. The skill defines how its required CLI (jamf-pro-cli) can be installed via the openclaw: frontmatter block.

OpenClaw isn't generally available yet; the frontmatter wiring is pre-shipped and will activate the moment OpenClaw launches.

Authenticate

Create an API client in each client's Jamf Pro (Settings > System > API roles and clients), with only the privileges your reports need. Then register each instance once. The secret stays in an environment variable you name, and is never written to the registry.

macOS / Linux:

export JAMF_PRO_FLEET_SECRETS="acme=<client-secret>"

jamf-pro-cli instance add acme --server acme.jamfcloud.com --client-id jamf-pro-cli instance test

Windows (PowerShell):

$env:JAMF_PRO_FLEET_SECRETS = "acme=<client-secret>"

jamf-pro-cli instance add acme --server acme.jamfcloud.com --client-id jamf-pro-cli instance test

instance test requests a new token for each instance and reads its Jamf Pro version, so it proves each API client works. With one server, set JAMF_PRO_SERVER, JAMF_PRO_CLIENT_ID and JAMF_PRO_CLIENT_SECRET instead and run jamf-pro-cli doctor: it requests a token and reads the Jamf Pro version with it.

What this skill does

Full command reference: guide.md. For the AI-agent operating contract (--agent, --dry-run, when to confirm before mutating), see AGENTS.md.

What makes this different

A connector that forwards each tool call to one Jamf Pro server answers for one client at a time. That's fine for one record. It stops working when you're asking "which of my 40 clients has FileVault off, and on how many Macs?"

This skill keeps a registry of every client's server and API client and reads them in parallel, each with its own credential, so that question is one command and one table with an instance column: fleet posture, fleet patch, fleet baseline. Those commands read live. sync also builds a local SQLite mirror per instance for offline search. An unsynced mirror answers empty, so sync first when you use --data-source local.

The pain this closes

Jamf Pro gives each customer its own server, so an MSP works many consoles. On Jamf Nation's "Multi-tenant Jamf Pro?" thread one MSP engineer put it as "about 100 instances", because Apple requires each organization to have its own push certificate. Any question across clients then means one login per client.

• jamf-pro-cli fleet find - the ticket names a Mac but not the client: find which client has it.
• jamf-pro-cli fleet health --within 30d - catch a lapsing ADE or VPP token before onboarding stops.
• jamf-pro-cli fleet posture --min-os 14.6 - per-client counts of stale check-ins, old macOS, FileVault off and firewall off.
• jamf-pro-cli fleet policy-hygiene - policies that can never run, before a client notices.
• jamf-pro-cli fleet baseline --golden msp-template - which clients are missing your template's policies, profiles and smart groups by name, or run a different copy of its scripts.

See pain-point.md for the longer narrative.

Frequently asked questions

Does this work with ChatGPT?

Yes, on Plus, Pro, Team, Business, Enterprise, and Education plans (Free tier does not yet expose Developer Mode). ChatGPT connects to remote MCP servers over HTTPS, not local stdio binaries. The Jamf Pro MCP server runs locally over stdio by default. Its HTTP mode (`jamf-pro-mcp --tra