Jenzabar One MCP Server & Agent Skill

What is the Jenzabar One API, and what can an agent read from it?

Jenzabar says the Jenzabar One API supports custom integrations with Jenzabar One, and Unity Platform is a Boomi-based iPaaS with prebuilt integrations. No protocol, endpoint list or API reference is published.

• API: Jenzabar One API and Jenzabar Unity Platform (Mixed)
• Access: Issued by your administrator
• Authentication: not published by Jenzabar

No public developer portal or API reference. The API and Unity Platform are offered to Jenzabar customer institutions; third parties work through Jenzabar's Strategic Partnership Program via the Partner Team.

Jenzabar does not publish the API's authentication method. Institutions arrange integration access through their Jenzabar account team.

What can an agent read from Jenzabar One?

• Student records — Student module data (records, registration, academics) via the Jenzabar One API or Unity Platform; endpoints not public.
• Recruitment and admissions — Prospect and applicant data in the Recruitment module; endpoints not public.
• Financial aid — Financial aid module data such as awards; endpoints not public.
• Finance — Finance module data such as student accounts; endpoints not public.
• Human capital management — Employee and HR data in the HCM module; endpoints not public.

What can an agent write to Jenzabar One?

This skill only reads Jenzabar One data; it documents no write calls, so an agent built on it cannot change a Jenzabar One record.

Student records are FERPA-protected education records; financial aid and student account data are also GLBA nonpublic personal information; HCM holds employee personnel data.

How do I connect Jenzabar One to an AI agent over MCP?

As of October 2026 we found no MCP server published by Jenzabar itself.

The practical path is to host a small MCP server that wraps the Jenzabar One API and Jenzabar Unity Platform, or to give the agent the calls directly with the SKILL.md below.

On ibl.ai an MCP connection is three records, and a working integration always needs all three:

1. Register the server — POST …/mcp-servers/ with its URL, a transport (sse, websocket or streamable_http) and an auth_type of none, token or oauth2.
2. Create a connection that holds the credential, scoped to the whole organization (platform), to a single agent, or to each user (user).
3. Enable it on the agent — mcp-tool in tool_slugs and the server id in mcp_servers. Both lists are replaced, not merged, so read the settings first.

For an API key or a service credential, one token connection at platform scope serves the whole organization; scope a connection to a single agent when that agent needs narrower access than the rest.

The field reference is in MCP server connections, and the /iblai-api-agent-mcp skill runs all three steps from a coding agent.

What does the Jenzabar One agent skill do?

The Jenzabar One skill is one SKILL.md file named iblai-connect-jenzabar-one. It gives an agent the auth conventions, what to read, which writes need a person's confirmation, the ibl.ai MCP wiring, example prompts and guardrails.

Download the Jenzabar One SKILL.md

Save it as .claude/skills/iblai-connect-jenzabar-one/SKILL.md, or in your agent's skills folder. The ibl.ai platform skills it calls come from one install:

This connector skill is a starting point maintained on ibl.ai, not part of the iblai/vibe repository.

It was checked against Jenzabar's documentation on October 20, 2026. Test it against your own Jenzabar One setup before you rely on it.

What can I ask a Jenzabar One agent to do?

• “Pull this term's registration counts by program from Jenzabar One.”
• “List admitted students who have not yet completed financial aid paperwork.”
• “Show advisees with a GPA below 2.0 after midterm grades.”
• “Summarize unpaid student account balances by class year.”

How do I run a Jenzabar One agent on ibl.ai?

Agentic OS is where the agent runs on ibl.ai: it holds the Jenzabar One MCP connection, the model the agent uses, its instructions and its conversation history.

On ibl.ai you own all the code and the data, run it model-agnostic across any LLM, and pay with no per-seat pricing — so you can deploy anywhere, from your own cloud to a fully air-gapped network.

• AI agents for Higher Education — what ibl.ai deploys in this sector

Which ibl.ai agents work with Jenzabar One data?

• Student Life Guide — Higher Education
• Administrative Services Guide — Higher Education

Where does ibl.ai describe the Jenzabar One integration?

• Jenzabar One and ibl.ai — the integration overview

Which ibl.ai platform skills does a Jenzabar One agent use?

• /iblai-api-agent-mcp — MCP connectors for ibl.ai agents, end to end
• /iblai-vibe-agent-mcp — Add the agent MCP tab (Model Context Protocol connector management with featured connectors, custom connectors, OAuth,…
• /iblai-api-agent-tool — Enable or disable an ibl.ai agent's tools via the platform API

What else should I know before connecting Jenzabar One to an AI agent?

Which other data sources can an AI agent connect to alongside Jenzabar One?

Which other Higher Education systems have a connector?

• 1EdTech OneRoster — Rostering and gradebook data standard
• Blackboard Learn — Learning management system
• Canvas LMS — Learning management system
• D2L Brightspace — Learning management system
• EAB Navigate360 — Student success CRM
• Ellucian Banner — Student information system / ERP
• Ellucian Colleague — Student information system / ERP
• Encoura Reach (Anthology Reach) — Higher-education CRM
• Handshake — Career services and early-career recruiting platform
• Moodle LMS — Learning management system
• PeopleSoft Campus Solutions — Student information system
• Raiser's Edge NXT — Fundraising and donor CRM
• Salesforce Education Cloud — Education CRM
• Slate — Admissions CRM
• Workday Student — Student information system

Every connector, grouped by sector, is on the connectors hub.