What integrations contain
Every integration is built from the same set of standardized components. Not all integrations include every component — the table below describes what each one provides.| Component | Description |
|---|---|
| Connection flow | Secure authentication flow that connects your account without exposing credentials. Handles token exchange, refresh, and scope management. |
| Webhooks | Real-time event listeners that receive notifications from external services (e.g., a new issue created, a PR merged) and route them into Tembo. |
| Triggers | Named events (e.g., github.pull_request.opened) that can start Automations. Each trigger maps to a specific webhook event and can include filters. |
| MCP Server | A Model Context Protocol server that gives coding agents direct access to the integration’s API — querying issues, reading data, managing resources — while working on tasks. |
| Git Provider | Repository operations for source control integrations: cloning, branching, committing, and opening pull requests. |
Available integrations
Source Control
Connect your repositories so Tembo can scan code, open pull requests, and respond to review feedback.Work Collaboration
Assign tasks from project management and communication tools to trigger coding agents.Monitoring
Detect production errors and automatically generate fixes.| Integration | Connection flow | Webhooks | Triggers | MCP |
|---|---|---|---|---|
| Sentry | Yes | Yes | Yes | Yes |
Database Providers
Monitor database performance and generate optimization pull requests.Other
Installing an integration
Navigate to Integrations
Open the Integrations page in your Tembo dashboard.
Install or Connect
Click the Install or Connect button next to the integration you want to add. Connection flow integrations redirect you to the external service to authorize access. Non-OAuth integrations (like Postgres) ask for connection details directly.
MCP servers from integrations
When you connect certain integrations, MCP servers become automatically available to your coding agents. This means agents can query issues, read documentation, check error details, or run database queries in real-time while working on tasks — without any additional configuration. Integrations that provide MCP servers: GitHub, GitLab, Slack, Linear, Jira, Sentry, Notion, and Postgres.Automation triggers
Integrations that support triggers let you build Automations that start coding agents in response to external events. For example, you can configure an automation that runs when a GitHub issue is opened, a Sentry error is detected, or a Linear issue is assigned to Tembo. Each integration’s documentation page lists its supported trigger events and naming conventions (e.g.,github.pull_request.opened, sentry.issue.created, linear.issue.assigned).
Managing installed integrations
You can manage your installed integrations from the Integrations page:- Disconnect — Remove an integration by clicking the disconnect or uninstall button. This revokes Tembo’s access to the external service.