How do I get Jamf Pro API credentials?

You need to create an API user in your Jamf Pro console under Settings > User Accounts & Groups. Ensure the user has the necessary privileges for the data you want to access.

What is the instance domain?

The domain is your Jamf Pro server URL (e.g., company.jamfcloud.com). You must provide this during setup.

Does it support the latest Jamf Pro API?

Yes, this MCP uses the Jamf Pro API v1 with Bearer token authentication.

Jamf Pro MCP Server for VS Code Copilot 10 tools — connect in under 2 minutes

Name: Jamf Pro
Availability: InStock
Author: Vinkius

code.visualstudio.com/docs/copilot/chat/mcp-servers

Built by Vinkius GDPR 10 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Jamf Pro and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "jamf-pro": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Jamf Pro MCP Server

Empower your AI agents to manage your Apple ecosystem with Jamf Pro. This MCP server allows you to list mobile devices and computers, track inventory details, manage users and buildings, and view management scripts and packages directly through the Jamf Pro API. Ideal for automating IT operations and device management.

GitHub Copilot Agent mode brings Jamf Pro data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 10 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

The Jamf Pro MCP Server exposes 10 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Jamf Pro to VS Code Copilot via MCP

Follow these steps to integrate the Jamf Pro MCP Server with VS Code Copilot.

Create MCP config

Create a .vscode/mcp.json file in your project root

Add the server config

Paste the JSON configuration above

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

Start using Jamf Pro

Ask Copilot: "Using Jamf Pro, help me...". 10 tools available

Why Use VS Code Copilot with the Jamf Pro MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Jamf Pro through the Model Context Protocol.

VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

Jamf Pro + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Jamf Pro MCP Server delivers measurable value.

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Jamf Pro MCP Tools for VS Code Copilot (10)

These 10 tools become available when you connect Jamf Pro to VS Code Copilot via MCP:

get_computer

Includes disk encryption status, installed apps, and user info. Use this for detailed Mac auditing. Retrieves details for a specific computer

get_mobile_device

Includes OS version, security status, and assigned user. Use this for deep investigation of a specific mobile asset. Retrieves details for a specific mobile device

list_buildings

Useful for auditing site-based device distribution. Lists all configured buildings

list_categories

Useful for navigating the management hierarchy. Lists all management categories

list_computers

Includes computer names, IDs, and serial numbers. Essential for auditing the Mac fleet. Lists all managed computers

list_departments

Use this to analyze device distribution by business unit. Lists all configured departments

list_mobile_devices

Returns device names, IDs, and models. Use this to audit the mobile device fleet. Lists all managed mobile devices

list_packages

pkg, .dmg) available in the Jamf Pro distribution points. Useful for auditing available software deployments. Lists all software packages

list_scripts

) stored in Jamf Pro for remote execution. Useful for auditing custom automation assets. Lists all management scripts

list_users

Useful for identifying which users are associated with specific devices. Lists all users in the system

Example Prompts for Jamf Pro in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with Jamf Pro immediately.

"List all computers managed in Jamf Pro."

"Show me details for mobile device ID '456'."

"List all management scripts configured in the system."

Troubleshooting Jamf Pro MCP Server with VS Code Copilot

Common issues when connecting Jamf Pro to VS Code Copilot through the Vinkius, and how to resolve them.

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Jamf Pro + VS Code Copilot FAQ

Common questions about integrating Jamf Pro MCP Server with VS Code Copilot.

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.