ibl.ai MCP Configuration

Configure external tool access for AI agents (mentors) on the ibl.ai platform. The platform models MCP with three objects, and a working integration always requires all three:

MCP Server — metadata for the external MCP endpoint (name, URL, transport, auth_type, auth_scope).
MCP Server Connection — the credential binding (a static token, or a reference to an OAuth ConnectedService), at platform, agent, or user scope.
Agent wiring — the agent must have "mcp-tool" in its tools list AND the server ID in its mcp_servers list.

A missing step 3 is the most common failure mode: server and connection exist but the agent never calls them. Always finish by verifying agent settings.

Prerequisites (gather before doing anything)

Value	Notes
Base URL	e.g. `https://base.manager.iblai.app` (deployment-specific)
Org / tenant key	`{org}` in paths, e.g. `acme`
Admin username	`{user_id}` in paths. Must be a tenant admin for all create/update/delete operations
API token	Sent as `Authorization: Token <value>`
Agent (mentor) `unique_id`	UUID — needed for agent wiring or agent-scoped connections

ibl-mcp-config

ibl.ai MCP Configuration

Prerequisites (gather before doing anything)