> ## 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.

# Sazabi

> Search production logs, investigate issues, and trace errors back to code with Sazabi.

![Tembo and Sazabi logos](https://mintlify.s3.us-west-1.amazonaws.com/test-8862363a/images/integrations/sazabi.png)

## Features

* Plain-language search across your production logs through Sazabi's official MCP server (`https://mcp.sazabi.com/mcp`)
* Issues Sazabi has detected, with the context agents need to trace an error back to the code that caused it
* Investigations with the Sazabi agent, started from a Tembo session
* Log checks after a change ships, so Tembo can confirm a production problem is actually fixed
* Access limited to the Sazabi organization and projects you choose when you sign in

## Prerequisites

You need access to your Tembo organization and a Sazabi account with at least one project that is receiving logs.

## Installation

**1. Open Integrations**

In the Tembo app, go to **Settings → Integrations**.

**2. Install Sazabi**

Scroll to the **Monitoring** group and click **Install** next to Sazabi.

**3. Sign in to Sazabi and choose access**

Sign in with the Sazabi account you want to connect. On the **Authorize MCP connection** page, choose the organization the connection may act in. Under **Project access**, choose **All projects** or a single project, then click **Authorize**.

> [!NOTE]
>
> Each authorization covers one Sazabi organization. Choose a single project if Tembo only needs one service's logs.

**4. Confirm install**

After authorizing, you'll be redirected back to the Tembo Integrations page and Sazabi will switch from uninstalled to installed.

## Usage

Once installed, Tembo agents automatically have access to the Sazabi MCP server during sessions. No further configuration is needed in Tembo.

Start a new session and ask Tembo what errors a service threw in production over the last hour, or to look up a Sazabi issue and find the code that caused it. Confirm that the returned data belongs to the project you intended to connect before asking Tembo to make changes in Sazabi.

## Advanced

> [accordion] MCP server
>
> Every Sazabi API operation is available as an MCP tool, covering logs, issues, threads with the Sazabi agent, and dashboards. Depending on the client, the server lists each operation as its own tool or a compact `search` and `execute` pair. Every operation stays callable either way. See [Sazabi's MCP server reference](https://docs.sazabi.com/reference/mcp-server).

> [accordion] Permissions
>
> The connection acts as the Sazabi user who authorized it, limited to the organization and project access chosen on the authorization page. To switch organizations or change project access, uninstall Sazabi in **Settings → Integrations** and install it again.

> [accordion] Troubleshooting
>
> If the connection remains pending, return to **Settings → Integrations** and finish authorization. If tools do not appear, confirm the connection was saved and start a new session. If Tembo cannot find logs you expect, confirm the connection has access to the project that receives them. See [MCP troubleshooting](https://docs.tembo.io/integrations/mcp.md#advanced) for authentication and connectivity checks.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.