Overview & configuration
Connect Proliferate to the tools your team already uses.
Integrations connect Proliferate to the tools your team already uses, so agents can pull in real context and take action instead of waiting for you to copy-paste it. Connect Linear once and every agent session can check an issue. Connect Slack once and an agent can look up a thread you mention.
How it works
Connecting an integration is a two-part story:
- You connect your account. In Settings, you authorize Proliferate to reach a provider, either by signing in with OAuth or by pasting an API key. Proliferate stores that credential securely and never exposes it to the agent directly.
- Every session gets the tools automatically. Once your account is connected, any session you start, in any workspace, can call that provider's tools through Proliferate's own gateway. There's no per-session or per-workspace toggle to flip; connecting is enough.
Settings > Integrations, personal pane
The user integrations settings pane listing rows like Linear, Notion, and Slack, each with an auth-type label, tool count, a health badge (Ready, Not connected, Reconnect required), and Connect/Disconnect actions.
Your agent never sees your Linear token, Slack token, or any other credential. Proliferate holds those centrally and proxies each tool call on the agent's behalf.
Two ways to connect
- OAuth. Click Connect, sign in through your browser, and approve access. Most pre-registered integrations (Linear, Notion, Slack, GitLab, and more) work this way.
- API key. Paste a key generated from the provider's own dashboard. Integrations like Context7, Exa, Tavily, Render, and Neon work this way.
Some integrations need no credential at all. Cloudflare Docs, for example, is public documentation search and connects with one click.
See Pre-registered integrations for the full list of what Proliferate ships out of the box, and Adding an integration for the step-by-step connect flow.
Connections are personal
Every connected account belongs to the person who connected it. If you connect Notion, your sessions can use it; a teammate who wants the same needs to connect their own Notion account. Proliferate doesn't have a "team-shared" integration account today, even for tools an org admin has turned on for everyone.
Health status
Each connected integration shows a status so you always know whether an agent can actually use it:
| Status | What it means |
|---|---|
| Ready | Connected and working. |
| Not connected | You haven't connected this one yet. |
| Reconnect required | The connection expired or was revoked upstream; sign in again. |
| Error | Something's wrong with the connection that needs attention. |
| Disabled | You disconnected it. |
| Disabled by org | An admin turned this integration off organization-wide. |
If a connected integration needs attention mid-session, a small chip appears in the chat composer linking straight back to Settings, so you don't have to go looking for it.
Composer reauth chip
A quiet pill in the chat composer's input row, shown only when a connected integration reports Reconnect required, linking to Settings > Integrations.
Organization controls
Org admins get a separate pane for organization-wide policy: turning pre-registered integrations on or off for everyone, and registering custom integrations for internal or team-specific MCP (Model Context Protocol) servers.
Organization Settings > Integrations, admin pane
The org-admin integrations pane listing every visible definition (built-in and custom) with a Built-in/Custom badge, an enabled/disabled toggle, provenance text (Default: on / Set by org policy), and an Add custom MCP button.
Disabling a definition doesn't delete anyone's credentials, it just hides that integration from the gateway until it's turned back on. See Adding an integration for how admins register a custom one.