Manage Team models and MCP access

Control which models and MCP capabilities are available in a Kuse Team workspace, then test the policy with a member account.

Team governance can control which AI models and MCP capabilities members can use. Keep the available set aligned with the organization’s security, cost, and workflow requirements.

Decide the policy before changing controls

List the models or MCP capabilities required for approved work, who needs them, and any restrictions. Do not enable a capability only because it appears in the catalog.

Apply the workspace settings

Open the Team model or MCP settings available to your role, change the allowed set, and save. Catalog contents and control names can change, so document the policy outcome rather than relying on a fixed screenshot label.

Kuse Team MCP settings with the Add MCP server dialog open
Add an MCP server by entering its name, transport, URL, and any required headers.

Test with the affected role

After saving, use a member account to confirm what can and cannot be selected. Re-test important Workflows that depend on a model or MCP capability you changed.

Continue learning