Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.tembo.io/llms.txt

Use this file to discover all available pages before exploring further.

Pull requests are the most common output, but Tembo agents can take any action available through your connected integrations and MCP servers. A single session can span multiple repositories. Tembo can use context from connected integrations and MCP servers during the same session, make informed decisions, and open a pull request or merge request in each affected repository. It can also coordinate changes across different git providers when needed.

​
What agents can do

ActionIntegration
Open and update pull requestsGitHub, GitLab, Bitbucket
Post messages and summariesSlack
Create, update, and comment on issuesLinear, Jira
Create and update pagesNotion
Query databasesPostgres, Supabase, Neon, PlanetScale
Analyze errors and stack tracesSentry
Run browser automationKernel (Playwright)
Access analytics and feature flagsPostHog
Manage users and authClerk
Access payments and subscriptionsStripe
Access CRM dataAttio

​
Examples

Triage a Linear ticket in Slack: A Slack message triggers Tembo to read the Linear ticket, scan the codebase for context, and post an explanation back to the Slack thread. Summarize Sentry errors: A daily agent fetches errors from Sentry, ranks them by impact, creates Linear tickets, and posts a summary to Slack. Enrich issues with context: When a new issue is created, Tembo searches the codebase, pulls related Notion docs, and adds implementation hints as a comment. Query production data: During a session, an agent queries your Postgres database to understand the schema and writes a migration based on actual table structure. Ship a cross-repo change: One session updates multiple services, uses Linear and Sentry context to verify the work, and opens a PR or MR in each affected repository.

​
How it works

Agents access integrations through MCP servers. When you connect an integration or install an MCP server, it becomes available to agents during sessions and scheduled runs. No extra configuration needed. See MCP for available servers.