Integrations
Enable integrations org-wide and register a custom MCP server.
Org admins control two things here: which integrations are available inside the organization's scope, and registering a brand-new custom MCP server for the org. This governs org-scoped availability and calls, not a member's personal enrollment — connecting an account is still personal, done by each member from their own Settings, and remains 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 |
| Local / Cloud | Same either way; a session reads this regardless of where the agent runs |
Enable or disable an integration
Settings > Organization > Integrations lists every integration visible to your org — the built-in catalog plus anything registered as custom — each with a switch.
Disabling a row is firm governance inside org-scoped sessions, not identity-wide revocation. For a session running under your organization, a disabled integration drops out of the set the gateway will serve it and any further call to that integration fails. Because the gateway re-checks your organization's policy on every request, this reaches sessions that are already running, on their next tool call, not only newly started ones.
What it does not reach is a member's personal, organization-less setup: that path doesn't get the org policy overlay, so disabling here won't cut off calls made outside your organization's scope. Workflow runs draw their integration access from each workflow's own explicit grants rather than a member's chat defaults, but those grants still intersect with what's enabled for the organization here — a disabled integration is unavailable to a workflow run too (see Workflow integrations).
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.