Pre Registered
Integrations Proliferate ships pre-registered.
Pre-registered integrations are the ones Proliferate ships out of the box. Proliferate already knows how to reach each one, what credentials it needs, and what it's good for, so connecting one is a matter of clicking Connect and signing in or pasting a key. No org admin setup is required, though an admin can turn any of them off for the whole org.
If a tool you need isn't on this list, an org admin can register it as a custom integration as long as it exposes an MCP server. See Adding an integration for that flow.
What's pre-registered today
All of these are on by default and connect from Settings > Integrations.
| Integration | What it's for | Connects with |
|---|---|---|
| Linear | Issues, projects, cycles, and team state. | OAuth |
| Notion | Search and work with pages and databases you authorize. | OAuth |
| Slack | Search messages, channels, files, and users; prep follow-ups. | OAuth |
| Context7 | Current, version-specific docs and code examples for your project's libraries. | API key |
| Exa | Fast web, docs, and code search. | API key |
| Tavily | Web search plus extraction and crawl tools for deeper research. | API key |
| PostHog | Product analytics, feature flags, events, and observability context. | OAuth |
| Sentry | Issues, events, stack traces, projects, and releases. | OAuth |
| Axiom | Datasets, traces, logs, and monitor context. | OAuth |
| Supabase | Schema, SQL, storage, and config for one project at a time. | OAuth |
| Cloudflare Docs | Search official Cloudflare documentation and API references. | None |
| GitLab | GitLab.com projects, merge requests, issues, commits, and pipelines. | OAuth |
| Render | Services, deploys, logs, and infrastructure context. | API key |
| Neon Postgres | Neon projects, database branches, and schema, read-only. | API key |
Linear, Notion, and Slack have dedicated walkthroughs because they're the most commonly connected. The rest work the same way: find the row in Settings, click Connect, and follow the OAuth or API key prompt.
Personal, not shared
Every connection here is tied to the person who made it. If you connect Linear, your sessions get Linear tools; a teammate who wants the same needs to connect their own Linear account. There's no "connect once for the whole team" option today, even for integrations an org admin has turned on.
Org control
An org admin can enable or disable any pre-registered integration for the whole organization from Organization Settings > Integrations, independent of whether you personally connect it. Turning one off doesn't delete anyone's existing connection, it just hides it from the gateway until it's turned back on.
See Overview & configuration for how connections, health status, and org policy fit together.