Adding an integration
Connect an integration to your account, OAuth or API key.
This page covers connecting an integration to your own account, whether it's one Proliferate ships out of the box or a custom one your org admin registered. Registering a new custom integration is admin work, covered at the bottom of this page.
Connect an integration
See Catalog for everything Proliferate ships pre-registered.
Open Settings > Integrations
You need to be signed in to your Proliferate account. This list is personal to you, not shared across your team.
Find the integration and click Connect
What happens next depends on how the integration authenticates:
- OAuth (Linear, Notion, Slack, and most others): Proliferate opens your browser to the provider's own sign-in page. Approve access, then come back to the desktop app. The row waits with "Waiting for browser..." until the handoff completes. A few OAuth integrations also collect a setting during connect — Supabase asks for a project ref (and starts read-only) and PostHog asks for a region.
- API key (Context7, Exa, Tavily, Render, Neon): a dialog opens asking for the key, with a link or hint for where to generate one.
A custom integration your org admin registered connects the same way: OAuth if the admin set it up that way, or nothing at all if it needs no auth. Either way it never asks you for an API key of your own.
Confirm it's Ready
The row's badge flips to Ready. The integration is now eligible for new chat sessions, subject to your organization's defaults. Workflows receive it only when you grant it explicitly in the workflow editor.
Reconnecting and disconnecting
If a connection stops working, its badge changes to Reconnect required or Error, and the same row now offers Reconnect instead of Connect. To remove an integration entirely, click Disconnect and confirm. Agents immediately lose access to that integration's tools until you connect it again.
Disconnecting doesn't just hide the integration, it removes the stored credential. You'll need to reconnect from scratch, including OAuth consent, if you change your mind.
Registering a custom integration
Adding a brand-new integration, one Proliferate doesn't already know about, is an org-admin action, not something a member does from their own Settings. An admin registers it as a custom MCP server with OAuth (including dynamic client registration) or no authentication at all; custom integrations don't support connecting with an arbitrary API key.