iblai-api-agent-mcplisted

# iblai-api-agent-mcp Configure external MCP tool access for agents. The platform models MCP with three objects, and a working integration always requires all three: 1. **MCP server** — metadata for the external MCP endpoint (name, URL, transport, `auth_type`, `auth_scope`). 2. **MCP server connection** — the credential binding (a static token, or a reference to an OAuth connected service), at `platform`, `mentor` (agent), or `user` scope. 3. **Agent wiring** — the agent's settings must have the `mcp-tool` slug in `tool_slugs` AND the server id in `mcp_servers`. A missing step 3 is the most common failure mode: server and connection exist but the agent never calls them. Always finish by re-reading the agent's settings. ## Auth & conventions - **Base URL:** `https://api.iblai.app/dm` — the **`/dm` prefix is required**. MCP endpoints live under `/api/ai-mentor/orgs/{org}/users/{username}/...` and OAuth connector endpoints under `/api/ai-account/...`, appended to it. (`…` in the endpoint lists below abbreviates `https://api.iblai.app/dm/api/ai-mentor/orgs/{org}`.) - The backend also accepts an `agent`-spelled twin of every mentor route (`/api/ai-agent/...`, `agents/` for `mentors/`); the `mentor` spelling is canonical and used here, matching the other skills. - **Header:** `Authorization: Api-Token $IBLAI_API_KEY` on every request. - **Path vars:** `{org}` = `$IBLAI_ORG`, `{username}` = `$IBLAI_USERNAME`, `{mentor}` = the agent's unique id (UUID, e