Device Management
Jamf MCP connector
The Jamf connector brings your Macs, iPhones, iPads, users and admin accounts into Claude, ChatGPT, Cursor and any MCP client, so your team can look up, enroll and update managed devices in plain language.
-
How it connects. App credentials. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect Jamf to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Jamf once
-
Open Connections, choose Add connection, and pick Jamf.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste your Jamf app credentials. Jamf authenticates the app rather than a person. One person supplies the credentials once, and everyone else works through Share with.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Connect Jamf to Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Connect Jamf to ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Connect Jamf to Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Jamf to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Jamf through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
IT
Find every Mac that has gone quiet
Ask which computers in Jamf inventory have not checked in recently, then update the record once the machine is found or written off.
-
Support
Look up a device while the ticket is open
Pull the serial number, assigned user and installed apps for a colleague's iPhone or MacBook from Jamf without leaving the conversation.
-
Security
Spot phones still carrying an old app
List the mobile device applications in Jamf, find the versions that should be gone, and update or remove the entries that no longer belong.
-
People
Set up a new hire on day one
Create the person's Jamf user record, assign their laptop and phone, and confirm everything shows up before they walk in.
-
Operations
Reconcile the hardware list before a refresh
Compare what Jamf computer inventory says you own against what is on desks, then correct locations, models and owners in one pass.
-
IT
Review who holds a Jamf admin account
List every Jamf account, check who still needs elevated access, and remove or update the ones that should have gone months ago.
Try asking
- “List all Jamf mobile devices enrolled this month.”
- “Which Jamf users have no assigned mobile device?”
- “Show Jamf accounts with administrator privileges.”
AI tools
Jamf tools for your AI agents
25 tools are ready to call through Elaichi's MCP endpoint the moment you connect Jamf, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Jamf gets you
6 screens from the product, each doing one job for your Jamf account.
The agent
Ask about Jamf devices in plain language.
Starter prompts return live mobile devices, users and accounts from Jamf.
- accounts
- users
- mobile devices
- privileges
Ask Elaichi to work across your apps.
List all Jamf mobile devices enrolled this month.
Which Jamf users have no assigned mobile device?
Show Jamf accounts with administrator privileges.
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor reach Jamf.
One governed MCP endpoint over OAuth, no SDK and no shared API key.
Copy the endpoint
Tool catalog
25 Jamf tools ready without custom code.
Browse Jamf accounts, users and mobile device methods in one catalog.
- List all Jamf accounts
- Get single Jamf account by ID
- Delete a Jamf account by ID
- Update a Jamf account by ID
Toolboxes
Every team gets its own Jamf toolbox.
Toolboxes scope IT, security and helpdesk to the Jamf tools they need.
- IT operations
- Security
- Helpdesk
- Onboarding
Shared connections
Teammates use Jamf without seeing credentials.
The connections table shows who connected each Jamf account and its sharing.
- IT EMEA
- Security
- Helpdesk
- Onboarding
Audit log
Answer who touched which Jamf device.
Append-only entries record when, who, what happened, type and resource.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule drafts your Jamf device digest.
Six steps fetch mobile devices, group them, draft, await approval, post to Jamf.
Jamf digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch accounts
Jamf
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Jamf
Queued
Collections and dashboards
Jamf enrolment numbers land before anyone asks.
Four metrics, 14 days of new devices and a team breakdown, refreshed on schedule.
Jamf health
Refreshed 4 minutes ago · every 15 minutes · from the accounts collection
Accounts
1,284 ↓ 12%
Users
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Accounts created
Last 14 days
By team
Share of activity
IT EMEA 34%
Security 27%
Helpdesk 21%
Onboarding 18%
FAQ
Frequently asked questions
How do I connect Jamf to Claude?
Open Elaichi, choose Jamf from the connector catalog, and sign in with your Jamf app credentials. There is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. Claude will ask you to sign in to Elaichi as yourself, and your Jamf devices, users and accounts are available from then on.
Does Jamf work with ChatGPT and Cursor as well as Claude?
Yes. Once Jamf is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect Jamf once and every client you use picks it up.
What can an AI agent actually do with my Jamf data?
With Jamf connected, an agent can list and search your managed Macs, iPhones and iPads, look up a single device by its ID, and update inventory details like owner or location. It can also create and update Jamf users, review which apps are deployed to mobile devices, and manage the admin accounts that sign in to Jamf itself. In practice that means asking questions like which devices a person has, or which machines have not reported in, and getting an answer from live Jamf records.
Does connecting Jamf give the AI access to every device in my Jamf instance?
No. Every call to Jamf runs inside the access of the person who signed in, so an agent can only see and change the devices, users and accounts that person could already reach in Jamf. Elaichi can narrow that further, for example to read-only or to a subset of actions, but it can never widen it beyond what Jamf itself allows that person.
Can I stop an agent from deleting or changing things in Jamf?
Yes. Restrictions in Elaichi work per action, so you can allow looking up devices and users in Jamf while blocking deletes or edits entirely. A blocked action is never shown to Claude, ChatGPT, Cursor or any other client, so no prompt, however worded, can reach it.
What happens to a Jamf connection when someone leaves?
Offboarding a person in Elaichi ends their access to Jamf through every client at once, with no separate step in Claude, ChatGPT or Cursor. If they were using a shared Jamf connection, it keeps working for everyone else on the team. If you ever want Jamf gone completely, disconnecting it once in Elaichi removes it from every client at the same time.
Put Jamf in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.