Administration
MCP servers exist at a scope — a user, a team, an organization or the whole platform. Administrators decide which servers each scope can use and how they behave by default.
Scopes at a glance
- Personal — servers a user creates on the MCP page; visible only to them (and whoever they share with).
- Organization / Team — servers managed in the organization or team settings; members see them in their Actions list.
- Platform — system servers such as the core capabilities, managed by platform administrators.
Enable servers for an organization or team
In the organization settings, open the MCP section. The same management page appears for teams. From here administrators control what members can use:
- The switch activates or deactivates a server for everyone in the scope.
- Click Set as default to preselect a server in members' new conversations.
Confirmation defaults
On a server's page, each tool has an "Ask for confirmation by default" switch. Turn it on for tools that modify data or spend money: every run will pause and ask the user first.
Confirmation protects users
Users can always allow a tool for the rest of a conversation, but they cannot silence a confirmation you set as default. Keep it on for destructive actions.
Who can do what
All users
- Create, edit and delete their own MCP servers.
- Create and delete their own connections.
- Choose which enabled servers each of their conversations uses.
Organization & team administrators
- Activate or deactivate servers for their organization or team.
- Set scope defaults and manage servers owned by the scope.
Platform administrators
- Manage system servers and core capabilities.
- Full access to every server and every scope.
Best practices
- Enable confirmation by default for every tool that writes, sends or deletes.
- Keep tool selections minimal — fewer, well-described tools make the AI more accurate.
- Prefer per-user secret fields over shared all-users headers for anything sensitive.
- Review the connections and tools of shared servers regularly.