Adding an integration
Connect an integration to your account, OAuth or API key.
Connect an integration to your own account — either one Proliferate ships or a custom one your admin registered. Registering a new one is admin work, covered at the bottom.
Connect an integration
See the catalog for what ships pre-registered.
Open Settings > Integrations
Sign in first. This list is yours, not your team's.
Find the integration and click Connect
What happens next depends on how the integration authenticates:
- OAuth (Linear, Notion, Slack, most others): your browser opens to the provider's sign-in page. Approve, then come back. The row reads "Waiting for browser…" until the handoff finishes. Supabase also asks for a project ref and PostHog for a region.
- API key (Context7, Exa, Tavily, Render, Neon): a dialog asks for the key, with a hint for where to generate one.
A custom integration connects the same way — OAuth, or nothing at all if it needs no auth. It never asks you for a key of your own.
Confirm it's Ready
The badge flips to Ready. The integration is now eligible for new sessions, subject to your organization's defaults.
Reconnecting and disconnecting
A broken connection shows Reconnect required or Error, and the row offers Reconnect. Disconnect removes it entirely; agents lose those tools immediately.
Disconnecting removes the stored credential, not just the row. Changing your mind means going through OAuth consent again.
Registering a custom integration
Adding an integration Proliferate does not already know about is an admin action. Admins register it as a custom MCP server with OAuth (dynamic client registration included) or with no auth. Custom integrations cannot use an arbitrary API key.