What can AI agents do with Jamf Developer Portal through Ferentin?

Ferentin exposes 6 Jamf Developer Portal MCP tools to your AI agents, grouped as Discover (3 tools), Access (2 tools) and Manage (1 tool). Every call is checked against your Ferentin policies before it reaches Jamf Developer Portal.

How is Jamf Developer Portal access secured?

Requests through the Jamf Developer Portal integration are covered by no credentials required, public documentation only and tool level policy recommended. These controls are applied by Ferentin, not by Jamf Developer Portal, so they hold across every connected agent.

How do I connect Jamf Developer Portal to Ferentin?

Open the Ferentin admin console, add Jamf Developer Portal as a new connection and authenticate with the vendor credentials. You then choose which permissions and which tools your agents may use, and the connection goes live for everyone covered by your policies.

Is the Jamf Developer Portal integration generally available?

Yes. The Jamf Developer Portal integration is generally available on Ferentin, including the free tier.

Jamf Developer Portal

Generally Available

Navigate Jamf's OpenAPI specs to find the right endpoint and generate integration code.

Jamf
Documentation
API Reference

Configure Jamf Developer Portal Browse the 6 tools

Hosting: Vendor-hosted endpoint
Data actions: Read and write
MCP tools: 6

How it works

Every agent request passes through Ferentin policy before it reaches Jamf Developer Portal.

Ferentin connects with no credentials. An agent can search Jamf's endpoint catalog, read an endpoint's parameters and security schemes, and draft integration code — useful alongside Ferentin's own Jamf-backed device enrollment. The execute-request tool is a separate, higher-risk capability that should be governed explicitly.

AI agentAsks for something
Ferentin policies
- No credentials required
- Public documentation only
- Tool level policy recommended
Jamf Developer Portal MCP serverAuthorized connection
Governed resultMasked, logged, returned

What agents can do

6 tools · you choose which ones agents may call

Search and browse what exists, without opening the content itself.

List API Endpoints
Search API Endpoints
List OpenAPI Specs

Before you connect

This is a DEVELOPER-DOCUMENTATION server, not Jamf Pro device management. It does not enroll, inventory, or act on managed devices. It answers questions about Jamf's APIs and can issue HTTP calls on your behalf.
SECURITY — execute-request is an arbitrary-HTTP egress tool, not a Jamf-scoped one. Its input is a HAR object in which the caller supplies the method, the FULL destination URL, arbitrary headers, and an arbitrary body; the tool is annotated destructiveHint=true, openWorldHint=true. It is not restricted to Jamf hosts. A prompt-injected agent could use it to POST tenant data to an attacker-controlled URL, and any Jamf Pro credential passed to it transits Jamf's developer-portal infrastructure rather than going directly to your Jamf Pro instance.
RECOMMENDED POLICY — grant this server with an ALLOW policy that lists deny_toolsets: ["execute-request"], which keeps the five documentation tools while excluding the egress tool. Do NOT use a deny-effect policy for this: a deny-effect policy removes the whole server (instance-level deny precedence), not just the named tool.
The five exploration tools (list-specs, list-endpoints, get-endpoint, search-endpoints, get-server-variables) are all readOnlyHint=true and openWorldHint=false — they read Jamf's published OpenAPI specs and reach no other host.

3 more technical notes

Because the endpoint is unauthenticated, results are the same for every tenant and contain only Jamf's public API documentation. There is no per-tenant or per-user data behind this server.
Jamf publishes no .well-known/mcp-server-card — a request to that path returns the developer-portal HTML page, which naive discovery clients may misparse as a card.
Tool catalog captured live from the upstream on 2026-08-08 (6 tools, no prompts, no resources).

About Jamf Developer Portal

The Jamf Developer Portal publishes the OpenAPI specifications for Jamf Pro, Jamf School, and Jamf's other product APIs. Its MCP server exposes those specs to agents, plus a generic request-execution tool.

Website Developer docs

Frequently asked about Jamf Developer Portal

What can AI agents do with Jamf Developer Portal through Ferentin?: Ferentin exposes 6 Jamf Developer Portal MCP tools to your AI agents, grouped as Discover (3 tools), Access (2 tools) and Manage (1 tool). Every call is checked against your Ferentin policies before it reaches Jamf Developer Portal.
How is Jamf Developer Portal access secured?: Requests through the Jamf Developer Portal integration are covered by no credentials required, public documentation only and tool level policy recommended. These controls are applied by Ferentin, not by Jamf Developer Portal, so they hold across every connected agent.
How do I connect Jamf Developer Portal to Ferentin?: Open the Ferentin admin console, add Jamf Developer Portal as a new connection and authenticate with the vendor credentials. You then choose which permissions and which tools your agents may use, and the connection goes live for everyone covered by your policies.
Is the Jamf Developer Portal integration generally available?: Yes. The Jamf Developer Portal integration is generally available on Ferentin, including the free tier.