Integration catalog
The integrations Proliferate ships knowing how to reach, and how to connect one.
These are the integrations Proliferate already knows how to reach. No admin setup needed — 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 |
Every row connects the same way: click Connect, then sign in or paste a key. See Adding an integration.
Setup quirks
A few rows collect an extra setting during connect. Supabase asks for a project ref and starts read-only. PostHog asks for a region.
Notion
Notion's consent screen asks which pages and databases to share, rather than granting your whole workspace. Agents see only what you picked. To widen that later you have to reconnect and go through consent again.
Personal, not shared
Every connection belongs to the person who made it. A teammate needs their own; there is no connect-once-for-the-team option.
An admin can turn any row off org-wide regardless of who has connected it. See Admin.