Integrations
Enable integrations org-wide and register a custom MCP server.
Admins control two things: which integrations are available in the organization's scope, and registering a custom MCP server.
This governs org-scoped availability and calls, not personal enrollment. Connecting an account is still each member's own action from their Settings, and stays possible even when a row is off here. See Integrations.
| Who | Owner or admin |
| Affects | The organization — every member, current and future |
| Plan | No plan requirement |
Enable or disable an integration#
Settings → Organization → Integrations lists every integration visible to your org, built-in and custom, each with a switch.
Disabling a row is governance inside org-scoped sessions, not identity-wide revocation. A disabled integration drops out of what the gateway will serve, and further calls to it fail. The gateway rechecks policy on every request, so this reaches running sessions at their next tool call.
It does not reach a member's personal, organization-less setup — that path has no org policy overlay. A workflow step is an ordinary session, so disabling an integration here takes it away from workflow runs too.
See Integration catalog for what each built-in integration does.
Register a custom integration#
Adding an MCP server Proliferate doesn't already know about is admin-only.