Pydantic Logfire
Give the Sazabi agent tools to query OpenTelemetry traces and metrics, surface recent exceptions, and browse projects, alerts, and dashboards in Logfire.
About
Pydantic Logfire is an MCP connector that gives the Sazabi agent tools to query OpenTelemetry traces and metrics, surface recent exceptions, and browse projects, alerts, and dashboards. Logfire's MCP server authenticates via OAuth with dynamic client registration. Once connected, the agent works against your Logfire workspace hosted on Logfire's US region (logfire-us.pydantic.dev).
What the agent can do:
- Run arbitrary SQL queries against your Logfire datasets using the OpenTelemetry-native API
- Find the most recent exceptions in a given file
- Inspect the Logfire OpenTelemetry records schema to craft custom queries
- Browse projects, alerts, dashboards, channels, and variables
- Generate deep links into the Logfire UI for traces and issues
Prerequisites
- A Pydantic Logfire account in the US region (
logfire-us.pydantic.dev) - Permission to authorize third-party OAuth applications in your Logfire organization
Set up in the dashboard
Configure connectors in the dashboard under Settings > MCP connectors.
Open the connector
Find Pydantic Logfire in Settings > MCP connectors.
Authorize
Start the connection; Sazabi redirects you to Logfire to authorize, then back.
Set up with the CLI
You can also connect Pydantic Logfire with the Sazabi CLI (installed and authenticated — see sazabi mcp-connectors reference).
Pydantic Logfire authenticates over OAuth, so the CLI opens a browser to complete authorization:
sazabi mcp-connectors connect logfireAdd --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 (OAuth) or the key/header is correct (token auth).
Troubleshooting
No tools discovered — Disconnect and reconnect from Settings > MCP connectors to restart the OAuth flow.
Connection shows needs attention — The authorization or key may have expired or been revoked; reconnect from Settings > MCP connectors.