Better Stack
Give the Sazabi agent tools to investigate incidents, monitors, and log sources, and build telemetry queries directly from agent conversations.
About
Better Stack is an MCP connector that gives the Sazabi agent tools to investigate incidents, monitors, and log sources, and build telemetry queries. Better Stack's hosted MCP server authenticates via OAuth with dynamic client registration. Once connected, the agent can view incidents and on-call context, inspect uptime monitors and heartbeats, browse log sources, and build custom queries against your Better Stack Telemetry data. Write operations are governed by the per-connection read-only toggle.
What the agent can do:
- View incidents and on-call context
- Inspect uptime monitors and heartbeats
- Browse log sources and telemetry
- Build custom queries with AI against Better Stack Telemetry
Prerequisites
- An active Better Stack account
- Permission to authorize third-party OAuth applications in your Better Stack organization
Set up in the dashboard
Configure connectors in the dashboard under Settings > MCP connectors.
Open the connector
Find Better Stack in Settings > MCP connectors.
Authorize
Start the connection; Sazabi redirects you to Better Stack to authorize, then back.
Set up with the CLI
You can also connect Better Stack with the Sazabi CLI (installed and authenticated — see sazabi mcp-connectors reference).
Better Stack authenticates over OAuth, so the CLI opens a browser to complete authorization:
sazabi mcp-connectors connect better-stackAdd --read-only to restrict the connector to read-only tools, or --project-id <project> to target a specific project. In --json mode the command prints an authorization URL to open, then polls until the connection completes. Confirm the result with sazabi mcp-connectors list.
Verify
Open the connector's connection page under Settings > MCP connectors and confirm Sazabi lists the tools it discovered. Then, in a thread, ask the agent to use one of those tools and confirm it runs. If no tools appear, confirm the connection is authorized.
Troubleshooting
No tools discovered — Disconnect and reconnect from Settings > MCP connectors to restart the OAuth flow.
Connection shows needs attention — The authorization may have expired or been revoked; reconnect from Settings > MCP connectors.