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 CrewAI 10 tools — connect in under 2 minutes

Name: Jamf Pro
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to Jamf Pro through the Vinkius — pass the Edge URL in the `mcps` parameter and every Jamf Pro tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

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.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Jamf Pro Specialist",
    goal="Help users interact with Jamf Pro effectively",
    backstory=(
        "You are an expert at leveraging Jamf Pro tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token — get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Jamf Pro "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 10 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

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.

When paired with CrewAI, Jamf Pro becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Jamf Pro tools autonomously — one agent queries data, another analyzes results, a third compiles reports — all orchestrated through the Vinkius with zero configuration overhead.

The Jamf Pro MCP Server exposes 10 tools through the Vinkius. Connect it to CrewAI 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 CrewAI via MCP

Follow these steps to integrate the Jamf Pro MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py — CrewAI auto-discovers 10 tools from Jamf Pro

Why Use CrewAI with the Jamf Pro MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Jamf Pro through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles — one agent researches, another analyzes, a third generates reports — each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass the Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Jamf Pro + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Jamf Pro MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Jamf Pro for raw data, then a second analyst agent cross-references findings and flags anomalies — all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries Jamf Pro, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Jamf Pro tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries Jamf Pro against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Jamf Pro MCP Tools for CrewAI (10)

These 10 tools become available when you connect Jamf Pro to CrewAI 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 CrewAI

Ready-to-use prompts you can give your CrewAI 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 CrewAI

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

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts — check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

The Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Jamf Pro + CrewAI FAQ

Common questions about integrating Jamf Pro MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily — when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.