---
name: iblai-connect-jenzabar-one
description: "Read Jenzabar One data through the Jenzabar One API and Jenzabar Unity Platform and expose it to an ibl.ai agent as an MCP tool. Use when the user asks an agent to work with Jenzabar One data, or to set up a Jenzabar One MCP connection on ibl.ai."
metadata:
  kind: guide
---

# Jenzabar One connector for AI agents

> A starting point maintained on ibl.ai at https://ibl.ai/developer/connectors/jenzabar-one — not part of the iblai/vibe repository. Checked against Jenzabar's documentation on October 20, 2026; test it against your own Jenzabar One setup before you rely on it.

Jenzabar One is a cloud-delivered ERP and student information system for colleges. Modules cover student records, recruitment, retention, financial aid, finance, human capital management, advancement, communications and analytics.

## Auth & conventions

- **API:** Jenzabar One API and Jenzabar Unity Platform (Mixed). 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.
- **Access:** Issued by your administrator. 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.
- **Auth:** not published by Jenzabar. Jenzabar does not publish the API's authentication method. Institutions arrange integration access through their Jenzabar account team.
- Keep Jenzabar One credentials in environment variables or the ibl.ai credential store. Never print a token in chat and never commit one to a file.
- Destructive or outward-facing calls are marked **Confirm with the user first** — do.

## Reads

- **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.

## Writes

- None. This skill only reads Jenzabar One data.

## Expose it to an ibl.ai agent (MCP)

Jenzabar did not publish an MCP server of its own when this skill was checked. Host a small MCP server that wraps the calls above, then register it below.

First install the ibl.ai platform skills and connect your organization (writes `IBLAI_ORG`, `IBLAI_USERNAME` and `IBLAI_API_KEY` to `.env`):

```bash
npx skills add iblai/vibe --all
# then, in your coding agent:
/iblai-api-login
```

Every call below sends `Authorization: Api-Token $IBLAI_API_KEY`.

1. **Register the server** — `POST https://api.iblai.app/dm/api/ai-mentor/orgs/$IBLAI_ORG/users/$IBLAI_USERNAME/mcp-servers/` with `name`, `url`, `transport` (`sse` | `websocket` | `streamable_http`) and `auth_type` (`none` | `token` | `oauth2`). Capture the returned `id`.
   - For an API key or service credential use `auth_type=token` with `auth_scope=platform` for one key across the organization, or scope it to a single agent for one key per agent.
2. **Create the connection** — `POST https://api.iblai.app/dm/api/ai-mentor/orgs/$IBLAI_ORG/users/$IBLAI_USERNAME/mcp-server-connections/` with `server`, `scope` (`platform` | `mentor` | `user`), `auth_type`, and either `credentials` + `authorization_scheme` or a `connected_service` id for OAuth. Credentials are masked on read; never send a masked value back.
3. **Enable it on the agent** — `GET https://api.iblai.app/dm/api/ai-mentor/orgs/$IBLAI_ORG/users/$IBLAI_USERNAME/mentors/{agent_id}/settings/`, add `mcp-tool` to `tool_slugs` and the server id to `mcp_servers`, then `PATCH` the full lists back. They are replaced, not merged.

Full reference: https://ibl.ai/developer/platform/mcp/mcp-connections and the `/iblai-api-agent-mcp` skill.

## Example prompts

- "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."

## Guardrails

- Student records are FERPA-protected education records; financial aid and student account data are also GLBA nonpublic personal information; HCM holds employee personnel data.
- Request the narrowest Jenzabar One scopes or role the task needs, and prefer a read-only credential for agents that only answer questions.
- Return the fields the user asked for, not whole records; do not paste personal data into chat that the user did not request.
- Before any write, show the user exactly what will change and wait for a yes.
- Page through large result sets and back off on rate-limit responses instead of retrying in a loop.

## References

- Jenzabar One: https://www.jenzabar.com/jenzabar-one
- Jenzabar integration solutions: https://www.jenzabar.com/solution/integration-solutions
- Jenzabar Unity Platform: https://www.jenzabar.com/product/unity-platform
- This connector on ibl.ai: https://ibl.ai/developer/connectors/jenzabar-one
- ibl.ai MCP server connections: https://ibl.ai/developer/platform/mcp/mcp-connections