Skip to main content
Sazabi connects to other tools in four ways. Each vendor in the sidebar has one page that lists every way it connects, and each connection method has its own setup page. Many vendors connect in more than one way, for example Datadog as both a log source and an MCP connector. Each connection is set up separately: connecting one method does not enable the others.
  • Integrations connect source control, chat, work tracking and incident tools at the organization level.
  • Log sources send logs, metrics and traces to Sazabi.
  • MCP connectors give the Sazabi agent tools from an external service.
  • Sandbox CLIs give the Sazabi agent command-line tools in its sandbox.

Integrations

Integrations are organization-level connections you set up under Settings > Integrations. They give Sazabi features rather than data: code search and pull requests from source control, the agent in your chat tool, issues in your work tracker, incident notifications in your on-call tool, and issue fixes handed to your coding agent. Each page covers setup, the features it turns on, and how to verify it. To hand an issue to a cloud agent, choose Fix on the issue. The agent works in your repository and opens a pull request, and Sazabi follows the attempt in the issue thread.

Log sources

A log source is where your data comes from. Sazabi supports two ways to set one up. For a decision guide, see Choose a path.

Native: connect your account

Native log sources use the connect-your-account path: authorize a supported platform account and Sazabi configures forwarding for you. There is no collector to run. Some of these vendors also have a manual path; use that one instead when you run your own collector or want explicit control over what you forward.

Manual: send to an endpoint

Manual log sources use the send-to-an-endpoint path: Sazabi provides a keyed intake URL, and you configure your platform, collector, SDK, or agent to send to it. Copy the URL from Settings > Log streams (the public key is embedded in the URL). Use this path when you run your own collectors, instrument application code, or your platform is not in the native list. Manual describes the setup, not the delivery frequency: once configured, your sender can stream logs continuously. Telemetry from coding agents such as Claude Code, Codex, and Cursor uses the manual path and has its own coding agent telemetry list.

MCP connectors

An MCP connector gives the Sazabi agent tools from an external service through the Model Context Protocol, so the agent can act in that service during an investigation. Configure connectors in the dashboard under Settings > MCP connectors. To use Sazabi from your own coding agent instead, see Connect your coding agent.

Sandbox CLIs

The Sazabi agent runs commands in a sandbox. A sandbox CLI is a command-line tool baked into that sandbox, with a place to connect the tool’s credentials; connecting one creates a CLI connection. Configure the sandbox in the dashboard under Settings > Sandbox CLIs. For how the sandbox works, see Set up the sandbox.