Organization MCP Servers
Organization MCP servers let a team expose shared tools or data sources to organization-owned agents.
Open MCP server management at https://your-deployment.example/app/integrations.
When to use organization scope
Use organization scope when:
- Multiple team-owned agents need the same tool server.
- The server uses organization-managed credentials.
- Admins should control assignments.
- A personal MCP server would create continuity risk.
Use personal scope for experiments or user-specific tools.
Setup flow
- Create the MCP server.
- Choose the connection type supported by your deployment.
- Configure authentication or OAuth.
- Test the server.
- Assign it only to the agents that need it.
- Send a controlled test prompt and inspect timeline tool activity.
Assignment policy
Ordinary Organization-scoped servers require explicit agent assignments. Team-scoped servers stay within their Team. Product-managed integrations can be inherited by eligible agents in their workspace and do not accept manual assignment; configure those through the integration's own controls. Active configuration, authentication, and sandbox policy still determine whether tools are usable.
Avoid assigning broad tool servers to every agent by default. Assign based on role:
- Research agents may need search or data tools.
- Operations agents may need internal systems.
- Customer-facing agents may need stricter write approvals.
- Demo agents should usually have limited tools.
For user-level MCP concepts, see MCP Servers.