Administering AI settings
AI settings provide a centralized interface for enabling AI features, managing IBM watsonx® models, registering Model Context Protocol (MCP) servers with agents, and controlling multi‑agent execution. By centralizing AI configuration in a single location, AI settings help ensure consistent behavior across the platform, supports governance requirements, and reduces the risk of unintended or uncontrolled AI usage.
About this task
- Core areas of AI settings
- AI settings are structured around the following core areas, each of which addresses a specific
aspect of AI governance and execution.
- AI enablement and governance - AI capabilities are available on an explicit opt‑in basis, and administrators must review and accept all applicable AI usage and model‑specific licensing terms to enable AI functionality. This approach helps ensure that AI features are enabled intentionally and in alignment with organizational policies. By requiring explicit acceptance of terms, AI settings support transparency, compliance, and responsible adoption of AI features across environments.
- External tool integration - AI agents cannot directly call external systems or tools on their
own. An MCP server provides a controlled and governed way for agents to interact with external
services. By adding an MCP server, you define:
- Which external system an agent can access
- What actions (tool operations) the agent is allowed to perform
- How access is authenticated and secured
MCP servers are associated with specific agents, helping ensure that each agent can use only the external tools that are explicitly configured for it. Administrators register and configure MCP servers and explicitly enable the tool operations that agents are allowed to use. AI agents use only the tool operations that administrators make available, helping ensure controlled, and auditable access to external systems.
- Agent execution and orchestration - AI agents can run tasks independently or participate in coordinated execution through multi‑agent mode. In multi‑agent mode, the Coordinator orchestrates task execution across multiple agents, enabling collaboration and sequencing when required. This orchestration capability affects execution behavior only. Changing execution mode does not delete agents or modify their configurations, allowing administrators to adjust execution behavior without impacting agent definitions.
- Access and role‑based control
- Access to AI settings is restricted to users with specific administrative roles. Role‑based
access helps ensure that only authorized users can enable AI features and control agent behavior.
The following roles can view and use AI settings. Only users with one of these roles can enable or
disable AI features, manage MCP servers, control multi‑agent execution, and enable or disable tool operations.
- iPaaS admin - A subscription‑scoped role that allows management of AI settings across the entire subscription.
- Service admin - A service‑scoped role that allows management of AI settings only for the specific service to which the role is assigned.
- AI agents and configuration status
- AI agents perform AI‑assisted tasks by using AI models and available MCP tool operations. If AI access is disabled, agents and tools remain unavailable until access is re-enabled. AI settings provide visibility into the overall AI configuration, including agent status, MCP server connectivity, enabled tool operations, last updated timestamps, and availability of AI capabilities.
- Usage considerations
- When administering AI settings, keep the following considerations in mind.
- MCP servers must be configured and managed through the AI settings page.
- AI agents can use only the tool operations that administrators explicitly enable.