Manual Configuration¶

This guide covers the different ways to manually configure JamfMCP for various clients.

MCP Configuration Pattern¶

All MCP clients follow a similar pattern:

Specify the command to run JamfMCP
Set environment variables for authentication
Restart the client to load configuration

{
  "<server-name>": {
    "command": "<executable>",
    "args": ["<arg1>", "<arg2>", "..."],
    "env": {
      "<ENV_VAR>": "<value>"
    }
  }
}

FastMCP CLI Usage¶

The FastMCP CLI tool can assist in streamlining the process of configuring the JamfMCP locally. Reference FastMCP docs for your specific AI Platform:

Installation-specific Configuration¶

Depending how you chose to install JamfMCP, the configuration file syntax differs ever so slightly.

Note

The JSON examples below are only of the JamfMCP configuration. Actual MCP configurations will have a top-level key "mcpServers" that the JamfMCP configuration would be nested under.

uvx

{
  "jamfmcp": {
    "command": "uvx",
    "args": ["jamfmcp"],
    "env": {
      "JAMF_URL": "https://your-instance.jamfcloud.com",
      "JAMF_CLIENT_ID": "your-client-id",
      "JAMF_CLIENT_SECRET": "your-client-secret"
    }
  }
}

PyPI Installation (via pip)

{
  "jamfmcp": {
    "command": "uv",
    "args": [
      "run",
      "--with", "jamfmcp",
      "jamfmcp"
    ],
    "env": {
      "JAMF_URL": "https://your-instance.jamfcloud.com",
      "JAMF_CLIENT_ID": "your-client-id",
      "JAMF_CLIENT_SECRET": "your-client-secret"
    }
  }
}

Local Development

{
  "jamfmcp": {
    "command": "uv",
    "args": [
      "run",
      "--directory", "/path/to/cloned/jamfmcp",
      "fastmcp",
      "run",
      "src/jamfmcp/server.py:main"
    ],
    "env": {
      "JAMF_URL": "https://your-instance.jamfcloud.com",
      "JAMF_CLIENT_ID": "your-client-id",
      "JAMF_CLIENT_SECRET": "your-client-secret"
    }
  }
}

Environment Variables¶

Variable	Description	Required	Default
`JAMF_URL`	Jamf Pro server URL (include https://)	Yes	-
`JAMF_CLIENT_ID`	OAuth client ID	Yes	-
`JAMF_CLIENT_SECRET`	OAuth client secret	Yes	-

Configuration File Locations¶

Cursor

Global Location: ~/.cursor/mcp.json

Project-specific: .cursor/mcp.json in workspace

Claude

According to the following document, Claude Code and Claude Desktop both utilize the same file location for MCP server configurations:

~/Library/Application Support/Claude/claude_desktop_config.json