📅 Book a 30-min Demo📞 Call/text (571) 293-0242
Connectors

Connect any data source to an AI agent

Last updated

ibl.ai publishes 81 free connector skills — one SKILL.md for each data source an agent is most often asked to work with, from Slate and Ellucian Banner to Epic, Clio, Salesforce and QuickBooks. Each page states the vendor's API, its auth model and whether it ships its own MCP server, then shows how to run that agent on ibl.ai, where you own all the code and the data.

Every entry was checked against the vendor's own developer documentation on October 20, 2026. Where a system has no public API, its page says so and describes the integration path that does exist.

The 81 connectors cover 8 sectors. 37 of the vendors publish an official MCP server of their own, and 2 of the systems have no public API at all.

How do I connect a data source to an ibl.ai agent?

  1. Download the source's SKILL.md from its page below and save it in your coding agent's skills folder, for example .claude/skills/iblai-connect-slate/SKILL.md.
  2. Install the ibl.ai platform skills with npx skills add iblai/vibe --all, then run /iblai-api-login once to connect your organization.
  3. Wire the MCP connection — register the server, store the credential, and enable mcp-tool on the agent, as described in MCP server connections.
$ npx skills add iblai/vibe --all

Which data sources have a connector, by sector?

Higher Education (16)

K-12 (13)

Enterprise (21)

Government (10)

Financial Services (10)

Healthcare (7)

Small Business (12)

What is in each connector skill?

Each SKILL.md follows the same contract as the ibl.ai headless API skills, so an agent reads every connector the same way:

  • Auth & conventions — the vendor's API, base URL, auth model, who issues credentials, and documented limits.
  • Reads and writes — the objects an agent works with, with every destructive or outward-facing call marked “confirm with the user first”.
  • Expose it to an ibl.ai agent — the three MCP records and the exact platform endpoints.
  • Example prompts, guardrails and references — the data class to protect, and the vendor pages each fact was checked against.

Do I still need the vendor's own MCP server?

Only where you want it. When a vendor publishes an MCP server, its page links to it and you can register that server on ibl.ai unchanged. Otherwise the SKILL.md gives the agent the API calls, or you host a small MCP server that wraps them.

Either way the connection, the credential and the agent live in your ibl.ai deployment. The /iblai-api-agent-mcp skill registers servers and connections from a coding agent.

Where do these agents run?

Agentic OS runs the agent on ibl.ai: it holds the MCP connections, the model each 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.