apple-intune-baseline

An MCP server that turns mSCP (the macOS Security Compliance Project) baselines into Microsoft Intune configuration, for macOS and iOS/iPadOS. Ask your AI assistant for "CIS Level 1 for macOS 27" and get the Intune policies, compliance checks, remediation scripts and inventory for it, reviewed as local files before anything reaches your tenant.

It stays close to mSCP: rules, baselines, sections and organization-defined values come from mSCP's own Python code, pinned to an mSCP release. The server runs locally on your Mac and needs no other MCP server.

What you get

A baseline has four parts, each generated as local files and pushed separately:

Before generating, it checks what your tenant already configures and verifies, so nothing is duplicated. Afterwards it reads per-device results back into an interactive dashboard, PDF and CSV.

Baselines: everything mSCP ships, e.g. CIS Level 1 and 2, NIST 800-53 (low, moderate, high), NIST 800-171, CMMC, DISA STIG, for macOS 27.0 and 26.0 and iOS/iPadOS 27.0 and 26.0. You can tailor a copy: exclude rules with a reason, add rules, change organization-defined values.

Related MCP server: IntuneRW-Core

Safety

• Generating only writes local files. Review them before you push.

• Pushing shows a plan first (create, skip because the name exists, replace) and creates only after you confirm.

• Everything is created unassigned. Nothing reaches a device until you assign it in Intune, ideally to a pilot group first.

• Nothing is ever deleted. Existing policies are only overwritten when you name them in replace.

• Read-only by default. The app registration it creates for you can only read your tenant unless you choose the full permission set.

• Settings that change how people sign in (password policy, login window) and payloads that need configuration before pushing are flagged as heads-ups. Test on a device you can recover.

Install

Requires macOS (sign-in tokens live in the Keychain) and uv (brew install uv). uv fetches Python 3.12+, this server and the pinned mSCP release; the first start takes about a minute while mSCP is built, later starts come from uv's cache.

Claude Code:

claude mcp add apple-intune-baseline -- uvx --from git+https://github.com/SSMacAdmin/apple-intune-baseline@v0.1.0 apple-intune-baseline

Claude Desktop: add to ~/Library/Application Support/Claude/claude_desktop_config.json, using the full path from which uvx (Claude Desktop doesn't see your shell's PATH), then restart Claude Desktop:

{
  "mcpServers": {
    "apple-intune-baseline": {
      "command": "/opt/homebrew/bin/uvx",
      "args": ["--from", "git+https://github.com/SSMacAdmin/apple-intune-baseline@v0.1.0", "apple-intune-baseline"]
    }
  }
}

Other MCP clients: run the same uvx command as a stdio server.

Updating: change @v0.1.0 to the new release tag and restart the client. Your workspace (~/.apple-intune-baseline: tenants, prefixes, generated files, reports) stays where it is.

Quick start

Ask your assistant, in your own words:

1. "Which mSCP baselines are there for macOS 27?" and "Give me an overview of CIS Level 1": what each baseline delivers, and the rules users will notice.

2. "Connect to my Intune tenant": creates a read-only app registration once (you approve in the browser), then signs in.

3. "What does my tenant already cover of CIS Level 1?"

4. "Generate CIS Level 1 for macOS 27": profiles first, then it offers compliance, remediation and inventory.

5. "Push the policies": shows the plan, creates them unassigned after you say yes. Pushing needs the full permission set.

6. After assigning to a pilot group: "How are my Macs doing on CIS Level 1?"

Tools

Every baseline tool takes platform: macos (default) or ios (iPhone and iPad), and os_version (default: the newest).

Explore

Tenants and sign-in

Tailor, generate and push

Results

Resources: mscp://baseline/{platform}/{name} and mscp://rule/{platform}/{rule_id}. Prompt: review_baseline.

How each part behaves in detail (naming, device requirements, supervised and unsupervised sets, prefixes, the scripts, the workspace layout): docs/reference.md.

Permissions

setup_app_registration signs in once with Microsoft Graph PowerShell's public client (as Connect-MgGraph does), then creates a single-tenant public client app (http://localhost redirect, no secret) with delegated permissions, its Enterprise App, optional assignment to only you, and admin consent. The setup tokens are kept in memory only and dropped afterwards. Re-running updates the app with the same name.

tenants.json in the workspace holds only the tenant ID, client ID, default domain and permission set. No secrets are stored.

Known limitations

• A tenant is needed to generate. Settings Catalog policies are built from Microsoft's setting definitions, which are read through a tenant. A read-only connection to any tenant (e.g. a Microsoft 365 developer tenant) is enough; pass skip_configured=false so nothing is compared with it.

• Confirming a push isn't tied to the plan you saw. The agent is told to show the plan and wait for your yes, and MCP clients ask before running these tools, but a call with confirm=true runs whatever the current plan is.

• Not checked for coverage yet: device configuration templates (Device restrictions, Endpoint protection).

• Runs on macOS only.

License

MIT, see LICENSE. mSCP is a project of NIST and its contributors and is installed from its own repository under its own terms. This project isn't affiliated with or endorsed by NIST, Apple or Microsoft.