Jamf
MCP server for Jamf - search developer documentation and generate code for Jamf API integrations
Tools
6 available tools
Search the tool definitions captured from the MCP server. The live list can vary with version, deployment, and credentials.
6 tools found.
Execute request
Tool name:
execute-requestExecutes an API request with a given HAR request object.
Get endpoint
Tool name:
get-endpointGets detailed information about a specific API endpoint, including security schemes and servers
Get server variables
Tool name:
get-server-variablesGets the server variables for each server within a specific OpenAPI spec.
List endpoints
Tool name:
list-endpointsLists all API paths and their HTTP methods with summaries, organized by path.
List specs
Tool name:
list-specsLists all available OpenAPI specs.
Search endpoints
Tool name:
search-endpointsPerforms a deep search through paths, operations, and parameters to discover relevant API endpoints.
Compatibility
Connect Jamf to the clients your teams already use
27 AI clients can connect to Jamf through Runlayer. Pick one for its setup steps and controls.
Why Runlayer
Why connect Jamf through Runlayer?
One approved path
Approve Jamf once and everyone gets it in the AI clients they already use. Runlayer holds the credentials, so nothing sits in client configuration.
Fine-grained policy
Control who can use each server, tool, and resource, and under which runtime conditions.
Runtime security
Scan tool inputs and outputs for prompt injection, credential exposure, PII, and data exfiltration, then alert, mask, or block.
Audit and observability
Trace every request across users, clients, tools, policies, scanner decisions, and downstream systems.