Integration catalog
The integrations Proliferate ships knowing how to reach, and how to connect one.
The integration catalog is what Proliferate already knows how to reach: no admin setup needed before you can turn one on for yourself. Connect any row from Settings > Integrations.
The catalog
| 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 |
| 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 |
Connecting is the same for every row: find it in Settings, click Connect, and sign in or paste a key. See Adding an integration for that flow in detail.
Setup quirks
Most rows above have nothing special beyond the standard OAuth or API-key prompt. A few OAuth rows also collect a setting during connect — Supabase asks for a project ref and starts read-only, and PostHog asks for a region. Notion is worth calling out on its own.
Notion
Notion's consent screen asks you to pick which pages and databases to share, rather than granting access to your whole workspace. Agents only see what you selected. If you need to share more later, you have to reconnect and grant the broader access during a new consent flow, there's no way to add scope without going through it again.
Personal, not shared
Every connection is tied to the person who made it. A teammate who wants the same tool needs to connect their own account; there's no "connect once for the whole team" option today.
An org admin can turn any row off for the whole organization independent of who's personally connected it. See Admin for organization-wide controls.