There are two things you might mean by "adding an integration": connecting your own account to one Proliferate already knows about, or, if you're an org admin, registering a brand-new MCP server for your organization. Both are covered here.

Connect a pre-registered integration

Most people just need this. See Pre-registered integrations for the full catalog Proliferate ships out of the box.

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.
API key (Context7, Exa, Tavily, Render, Neon, and similar): a dialog opens asking for the key, with a link or hint for where to generate one. Some integrations also ask for a setting alongside the key, like a project ref for Supabase or a region for PostHog.

Confirm it's Ready

The row's badge flips to Ready, and any session you start from now on can use that integration's tools.

API key connect dialog

The Connect dialog for an API-key integration (for example Render), showing a password-masked key field with helper text, any required settings fields, and Cancel/Connect buttons.

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.

Register a custom integration (org admins)

If your team relies on an internal tool or a provider Proliferate doesn't pre-register, an org admin can add it directly as long as it exposes an MCP server.

Open Organization Settings > Integrations

This is a separate, admin-only pane from the personal one above. It lists every integration visible to your org, built-in and custom, with an enabled/disabled switch for each.

Click Add custom MCP

Fill in three fields:

Display name: what members see, for example "Internal tools".
Namespace: a short lowercase identifier (letters, digits, _, -) that prefixes the integration's tool names for agents.
MCP URL: the https:// endpoint of the MCP server itself.

Save and enable

The new integration is automatically enabled for your org. Members can start using its tools right away, no separate connection step required on their end, since custom integrations don't carry a personal credential today.

Add custom MCP integration dialog

The org-admin dialog for registering a custom integration, with Display name, Namespace, and MCP URL fields plus inline validation errors.

Custom integrations connect over a plain MCP endpoint with no credential step today. If the tool you're adding needs auth, put that behind the URL itself (for example a pre-signed or org-internal endpoint) rather than expecting a login prompt.

Turning integrations on and off

From the same admin pane, toggle any built-in or custom integration on or off for the whole organization. Turning one off doesn't touch anyone's personal connection, it just stops the gateway from surfacing it until an admin turns it back on.

Next: see Overview & configuration for how health status and org policy fit together, or Built-in agent capabilities for what ships directly in the product instead of through a connection.

Adding an integration