Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Jamf Pro MCP

by servosityversion 0.1.0i★ –iRuns on your computer
Registry nameio.github.Servosity/jamf-pro-mcp

Install

Overview

Description from the maker (original English)

Every client's Jamf Pro in one CLI: find devices, check posture and patch status, audit policies.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Developer tools
  • You need to fill in: JAMF_PRO_CLIENT_ID, JAMF_PRO_CLIENT_SECRET, JAMF_PRO_SERVER, JAMF_PRO_MCP_HTTP_TOKEN, JAMF_PRO_FLEET_SECRETS, PRINTING_PRESS_CLIENT_PROFILE

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • You fill in yourself: JAMF_PRO_CLIENT_ID, JAMF_PRO_CLIENT_SECRET, JAMF_PRO_SERVER, JAMF_PRO_MCP_READ_ONLY, JAMF_PRO_NO_LOCAL_DATA, JAMF_PRO_MCP_HTTP_TOKEN, JAMF_PRO_BASE_URL, JAMF_PRO_OAUTH_SCOPE, JAMF_PRO_FLEET_DIR, JAMF_PRO_FLEET_SECRETS, JAMF_PRO_INSTANCE, JAMF_PRO_USER_AGENT, PRINTING_PRESS_CLIENT_PROFILE

Values marked secret are keys to your account. Never share them or paste them into a chat.

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Download the maker’s .mcpb file

The link goes to the maker’s own file; we do not host or repackage it. Open the file and Claude Desktop installs it.

Run this in your terminal

Fill in the empty values before running it.

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • JAMF_PRO_CLIENT_ID secret required env
    The client ID of a Jamf Pro API client (Settings > System > API roles and clients).
  • JAMF_PRO_CLIENT_SECRET secret required env
    The client secret of that Jamf Pro API client.
  • JAMF_PRO_SERVER required env
    Your Jamf Pro server host, for example acme.jamfcloud.com.
  • JAMF_PRO_MCP_READ_ONLY env
    Optional. Set to exactly 1 to expose only read-only tools and refuse any state-changing execute call.
  • JAMF_PRO_NO_LOCAL_DATA env
    Optional. Set to 1 to keep no local copy of API responses: reads go to the API and the response cache is off.
  • JAMF_PRO_MCP_HTTP_TOKEN secret env
    Required only when running the MCP server with --transport http. Not needed for the default local stdio transport.
  • JAMF_PRO_BASE_URL env
    Optional. Overrides the API base URL; leave blank to use your Jamf Pro server.
  • JAMF_PRO_OAUTH_SCOPE env
    Optional. Scope sent when requesting a token; leave blank unless your API client needs one.
  • JAMF_PRO_FLEET_DIR env
    Optional. Folder holding the registry of client instances; leave blank for the default.
  • JAMF_PRO_FLEET_SECRETS secret env
    Optional. name=secret pairs (comma-separated) for instances registered with instance add; used by the fleet tools and an instance pin.
  • JAMF_PRO_INSTANCE env
    Optional. Name of a registered instance to point every single-server tool at.
  • JAMF_PRO_USER_AGENT env
    Optional. Overrides the User-Agent header sent to Jamf Pro; leave blank for the default.
  • PRINTING_PRESS_CLIENT_PROFILE secret env
    Optional: binds the MCP server to an existing tenant-gated Printing Press client profile. Leave unset for a single-tenant install.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account servosity, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Developer toolsi

  • More stars than 0% of the other 4906 servers in this category
  • Published to the registry more recently than 95% of the other 4906 servers in this category
  • Basic checks equal to or better than 100% of the other 4906 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Jamf Pro MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: JAMF_PRO_CLIENT_ID, JAMF_PRO_CLIENT_SECRET, JAMF_PRO_SERVER, JAMF_PRO_MCP_HTTP_TOKEN, JAMF_PRO_FLEET_SECRETS, PRINTING_PRESS_CLIENT_PROFILE

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.0) reached the registry yesterday.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need MCPB on your computer.

What can I use instead?

In the same category: GitHub, Desktop Commander, Cloudflare MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

GitHub

by github

GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.

Computer or cloud★ 34,245MITUpdated 4 days ago
Install

Desktop Commander

by wonderwhy-er

MCP server for terminal commands, file operations, and process management

Runs on your computer★ 10,225MITUpdated 16 days ago
Install

Cloudflare MCP

by cloudflare

Cloudflare MCP servers

Runs in the cloud★ 4,446Apache-2.0Updated 14 months ago
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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):

Your AI agentHow to install the Jamf Pro skill
Claude DesktopRun installer, then Settings > Extensions to register jamf-pro-mcp (no JSON editing).
ChatGPT (paid plans)Run installer, host jamf-pro-mcp over HTTPS with JAMF_PRO_MCP_HTTP_TOKEN set, then register it as a Developer Mode connector if your connector settings can send the bearer token.
Codex CLIPaste the install prompt below.
Claude CodePaste the install prompt below.
Claude CoworkPaste the install prompt below.
GitHub Copilot (VS Code)Run installer, add jamf-pro-mcp to mcp.json under the servers key, then pick Agent mode.

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.

AgentWhat it takes
Microsoft 365 Copilot / Copilot StudioNot self-serve. Host jamf-pro-mcp over HTTPS with JAMF_PRO_MCP_HTTP_TOKEN set, then wire it into Copilot Studio (Tools > Add a tool > Model Context Protocol > Server URL) or a declarative agent, if it can send the bearer token. Needs a Copilot Studio license + tenant admin. See mcp-install.md.
Google GeminiGemini CLI is local - same as Claude Code. The Gemini app is remote - same HTTPS path as ChatGPT. See mcp-install.md.

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

Question your MSP keeps askingCommand
Which client has this Mac, iPad or iPhone, by serial, name, username or email?jamf-pro-cli fleet find C02XK1ABJG5H
Which clients have stale check-ins, Macs below a macOS floor, FileVault off or the firewall off?jamf-pro-cli fleet posture --stale-days 14 --min-os 14.6
Which patch titles are behind latest, and which clients have failed managed OS updates?jamf-pro-cli fleet patch --behind-only
A vendor advisory landed: which clients and computers have this app below the fixed version?jamf-pro-cli fleet app "Google Chrome" --below 129.0.6668.100
Which policies are disabled, can never run, have no scope, or point at a missing script or package?jamf-pro-cli fleet policy-hygiene
Which ADE or VPP tokens expire soon, which enrollment syncs failed, and which Jamf Pro versions are clients on?jamf-pro-cli fleet health --within 30d
Which clients are missing objects from our template instance, or run a different copy of its scripts?jamf-pro-cli fleet baseline --golden msp-template
Does every client's API client still work?jamf-pro-cli instance test

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

Only the beginning is shown; read the rest in the repo

Ask PopNx