Debugging production from your editor with the Logfire MCP server
Blog post from Pydantic
Pydantic Logfire’s hosted MCP server connects coding agents such as Cursor, Claude Code, and Codex to OpenTelemetry traces, logs, and metrics, allowing them to investigate production behavior alongside source code through SQL-based queries. Available through plugins or a remote MCP URL with OAuth or API-key authentication, it offers 51 tools for querying observability data and managing dashboards, alerts, notification channels, feature flags, and issue states, though its query tool handles most use cases. The system grounds agents with schema references, detects overly expensive queries, and can use a separate Python execution environment for complex multi-step investigations while reducing context usage. Demonstrations show agents locating exceptions, editing affected code, analyzing application behavior, and turning findings into dashboards and alerts, while production users Dosu and AutonomyAI report faster debugging and detection of post-deployment problems. The service is most useful for bugs evidenced in traces rather than broad codebase patterns, and users are advised to validate agent conclusions, restrict write permissions, and treat read access carefully because telemetry may contain sensitive or untrusted content.
| Trend | Post Mentions | Total Month Mentions | Posts | Companies | MoM |
|---|---|---|---|---|---|
| MCP | 44 | 2,241 | 148 | 72 | -74% |
| OpenTelemetry | 6 | 125 | 18 | 15 | -83% |
| AI Agents | 1 | 931 | 231 | 103 | -84% |
| LLM | 1 | 747 | 162 | 79 | -85% |
| Observability | 1 | 472 | 102 | 54 | -85% |
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.