GitHub
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
Descripción del creador (original en inglés)
Every client's Jamf Pro in one CLI: find devices, check posture and patch status, audit policies.
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
Elige la app de IA que usas y copia la configuración.
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_PROFILELos valores marcados como secretos son llaves de tu cuenta. Nunca los compartas ni los pegues en un chat.
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Descargar el archivo .mcpb del creador
El enlace lleva al archivo del propio creador; no lo alojamos ni lo reempaquetamos. Abre el archivo y Claude Desktop lo instalará.
Ejecuta esto en tu terminal
Completa los valores vacíos antes de ejecutarlo.
Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Este se ejecuta en tu computadora, y ChatGPT solo puede conectarse a servidores en internet. Elige otra app.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
JAMF_PRO_MCP_READ_ONLY envJAMF_PRO_NO_LOCAL_DATA envJAMF_PRO_BASE_URL envJAMF_PRO_OAUTH_SCOPE envJAMF_PRO_FLEET_DIR envJAMF_PRO_INSTANCE envJAMF_PRO_USER_AGENT envEsta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 7 nov 2026
El nombre en el registro se verificó con la cuenta de GitHub servosity, dueña del repo
Todavía no hemos leído este repo en GitHub
Todavía no hemos leído este repo en GitHub
Este se ejecuta en tu computadora; no hay endpoint en internet
Se ejecuta en tu computadora y usa ajustes locales en su lugar
Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
Debes completar: JAMF_PRO_CLIENT_ID, JAMF_PRO_CLIENT_SECRET, JAMF_PRO_SERVER, JAMF_PRO_MCP_HTTP_TOKEN, JAMF_PRO_FLEET_SECRETS, PRINTING_PRESS_CLIENT_PROFILE
Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).
El repo de GitHub cambió por última vez –, y la última versión (0.1.0) llegó al registro ayer.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas MCPB en tu computadora.
En la misma categoría: GitHub, Desktop Commander, Cloudflare MCP
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
MCP server for terminal commands, file operations, and process management
Cloudflare MCP servers
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
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.
The six agents MSP owners actually use (self-serve, works today):
| Your AI agent | How to install the Jamf Pro skill |
|---|---|
| Claude Desktop | Run 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 CLI | Paste the install prompt below. |
| Claude Code | Paste the install prompt below. |
| Claude Cowork | Paste 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.
Big install base, but an honest heads-up: these are the remote / enterprise path, not the local binary you just installed.
| Agent | What it takes |
|---|---|
| Microsoft 365 Copilot / Copilot Studio | Not 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 Gemini | Gemini 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.mddirectly *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.
.mcpbDownload 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
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, runiwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/jamf-pro/install.ps1 | iex. Then authenticate per the README and runjamf-pro-cli --helpto explore.
The same prompt works in any agent that can run shell.
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
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.
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.
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.
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 theopenclaw:frontmatter block.
OpenClaw isn't generally available yet; the frontmatter wiring is pre-shipped and will activate the moment OpenClaw launches.
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.
| Question your MSP keeps asking | Command |
|---|---|
| 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.
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.
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.
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
Solo se muestra el principio; lee el resto en el repo