InnerVault

Jamf Pro MCP

IndexedOfficial MCP Registry, io.github.Servosity

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

Open the source (opens github.com) https://github.com/servosity/msp-skills

Before you use it

  • Runs on your computer with your permissions. Read what it can do before connecting it to an agent.
  • Needs credentials: JAMF_PRO_CLIENT_ID, JAMF_PRO_CLIENT_SECRET, JAMF_PRO_FLEET_SECRETS, JAMF_PRO_MCP_HTTP_TOKEN, PRINTING_PRESS_CLIENT_PROFILE. Use a key with the least access you can.

What it is

MCP servers from io.github.Servosity.

The problem it solves and who it suits haven't been reviewed by InnerVault. The description above is the source's own.

How to get it

mcpb package (stdio)

https://github.com/Servosity/msp-skills/releases/download/jamf-pro-v0.1.5/jamf-pro-mcp.mcpb@0.1.5

From the server's entry in the official MCP Registry

Settings it asks for

  • JAMF_PRO_CLIENT_ID secret required · The client ID of a Jamf Pro API client (Settings > System > API roles and clients).
  • JAMF_PRO_CLIENT_SECRET secret required · The client secret of that Jamf Pro API client.
  • JAMF_PRO_SERVER required · Your Jamf Pro server host, for example acme.jamfcloud.com.
  • JAMF_PRO_MCP_READ_ONLY · Optional. Set to exactly 1 to expose only read-only tools and refuse any state-changing execute call.
  • JAMF_PRO_NO_LOCAL_DATA · 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 · Required only when running the MCP server with --transport http. Not needed for the default local stdio transport.
  • JAMF_PRO_BASE_URL · Optional. Overrides the API base URL; leave blank to use your Jamf Pro server.
  • JAMF_PRO_OAUTH_SCOPE · Optional. Scope sent when requesting a token; leave blank unless your API client needs one.
  • JAMF_PRO_FLEET_DIR · Optional. Folder holding the registry of client instances; leave blank for the default.
  • JAMF_PRO_FLEET_SECRETS secret · Optional. name=secret pairs (comma-separated) for instances registered with instance add; used by the fleet tools and an instance pin.
  • JAMF_PRO_INSTANCE · Optional. Name of a registered instance to point every single-server tool at.
  • JAMF_PRO_USER_AGENT · Optional. Overrides the User-Agent header sent to Jamf Pro; leave blank for the default.

Related

  1. Security Detections

    MCP servers

    Search security detections across Sigma, Splunk, Elastic, KQL, Sublime, CQL and Jamf with ATT&CK.

    Stale Official MCP Registry, io.github.MHaggis Updated 12 days ago 1 note

    security-detections-mcp@3.3.4
  2. Apify MCP server

    MCP servers

    Lets an agent run Apify's ready-made scrapers to pull data from websites, search engines, maps and social platforms.

    Hand-checked InnerVault (hand-checked), Apify 16.0k ★MIT

  3. GitHub MCP server

    MCP servers

    GitHub's official MCP server. It lets an agent read and work with repositories, issues and pull requests.

    Hand-checked InnerVault (hand-checked), GitHub 34.3k ★MIT

    https://api.githubcopilot.com/mcp/
  4. The open standard for connecting AI apps to tools and data. Start here to understand servers, clients, tools and resources.

    Hand-checked InnerVault (hand-checked), MCP project Moving from MIT to Apache-2.0 (code); see the project for docs licence

  5. Official MCP Registry

    MCP servers

    The MCP project's own registry of public MCP servers, so you can look for a connector before building one.

    Hand-checked InnerVault (hand-checked), MCP project Moving from MIT to Apache-2.0

  6. MCP reference servers

    MCP servers

    Small example servers from the MCP project (filesystem, git, fetch, memory and more) that show how MCP works.

    Hand-checked InnerVault (hand-checked), MCP project Moving from MIT to Apache-2.0