Pydantic Logfire
Overview
Pydantic Logfire is an AI-native observability platform built by the team behind Pydantic. It provides full-stack tracing for LLM applications using OpenTelemetry, combining AI-specific features (conversation panels, token tracking, cost monitoring, tool call inspection) with traditional application observability. Unlike AI-only observability tools that only see the LLM layer, Logfire traces the entire application stack, enabling debugging of both AI reasoning and backend infrastructure issues.
Problem Addressed
| Problem |
Solution |
| AI-only tools miss backend context |
Full-stack OpenTelemetry tracing shows what happened inside tool calls |
| Debugging LLM conversations is difficult |
Human-readable conversation panels with tool call inspection |
| Token usage and costs are opaque |
Built-in token tracking and cost monitoring across providers |
| Observability tools have proprietary query languages |
SQL-based analysis (PostgreSQL-compatible) queryable by AI agents |
| Existing tools cannot be queried by AI |
MCP server provides SQL access for AI agents to query production data |
| Pydantic validation errors are hard to trace |
Native Pydantic integration with validation analytics |
| Agent debugging requires multiple tools |
Single platform for traces, metrics, logs with agent-specific visualization |
| Streaming responses are hard to observe |
Full visibility into streamed chunks with dedicated span handling |
| Evaluations are UI-managed in other tools |
Code-first evaluations via pydantic-evals, version-controlled and CI-integrated |
| Lock-in with proprietary instrumentation |
Built on OpenTelemetry standard, data portable to any OTel backend |
Key Statistics
| Metric |
Value |
Date Gathered |
| GitHub Stars |
3,984 |
2026-02-05 |
| GitHub Forks |
204 |
2026-02-05 |
| Open Issues |
N/A |
2026-02-05 |
| Primary Language |
Python |
2026-02-05 |
| Python Requires |
>=3.9 |
2026-02-05 |
| Repository Age |
Since April 2024 |
2026-02-05 |
Key Features
AI/LLM Observability
- LLM Panels: Visual inspection of conversations, tool calls, and responses
- Token Tracking: Per-request and per-model token usage visibility
- Cost Monitoring: Spending tracking across providers with threshold alerts
- Tool Call Inspection: Arguments, responses, and latency for each tool call
- Streaming Support: Debug streaming responses with chunk-level visibility
- Multi-turn Conversations: Trace entire conversation flows across turns
LLM Framework Integrations
| Framework |
Integration Method |
| Pydantic AI |
logfire.instrument_pydantic_ai() |
| OpenAI |
logfire.instrument_openai() |
| OpenAI Agents |
logfire.instrument_openai_agents() |
| Anthropic |
logfire.instrument_anthropic() |
| Claude Agent SDK |
Via Langsmith OTel bridge |
| LangChain |
Built-in OTel support |
| LlamaIndex |
logfire.instrument_llamaindex() |
| LiteLLM |
logfire.instrument_litellm() |
| Google GenAI |
logfire.instrument_google_genai() |
| Magentic |
Built-in Logfire support |
| Mirascope |
@with_logfire decorator |
Web Framework Integrations
- FastAPI:
logfire.instrument_fastapi()
- Django:
logfire.instrument_django()
- Flask:
logfire.instrument_flask()
- Starlette:
logfire.instrument_starlette()
- AIOHTTP:
logfire.instrument_aiohttp_client(), logfire.instrument_aiohttp_server()
- ASGI/WSGI: Generic middleware support
Database Integrations
- Psycopg:
logfire.instrument_psycopg()
- SQLAlchemy:
logfire.instrument_sqlalchemy()
- Asyncpg:
logfire.instrument_asyncpg()
- PyMongo:
logfire.instrument_pymongo()
- MySQL:
logfire.instrument_mysql()
- SQLite3:
logfire.instrument_sqlite3()
- Redis:
logfire.instrument_redis()
- BigQuery: Built-in, no config needed
HTTP Client Integrations
- HTTPX:
logfire.instrument_httpx()
- Requests:
logfire.instrument_requests()
- AIOHTTP:
logfire.instrument_aiohttp_client()
Additional Integrations
- AWS Lambda:
logfire.instrument_aws_lambda()
- Celery:
logfire.instrument_celery()
- Airflow: Built-in, config needed
- FastStream: Built-in, config needed
- Pytest:
pytest --logfire plugin
- Standard Logging: Integration with logging, loguru, structlog
- System Metrics:
logfire.instrument_system_metrics()
- Stripe: Via HTTP instrumentation
Platform Features
- SQL Query Interface: PostgreSQL-compatible SQL for data analysis
- MCP Server: Native Model Context Protocol server for AI agent querying
- Live View: Real-time trace visualization dashboard
- Natural Language Search: LLM-powered SQL generation via Pydantic AI
- Standard Dashboards: Pre-built dashboards for web server metrics, system metrics
- Evaluations: Integration with pydantic-evals for code-first testing
Technical Architecture
Stack Components
| Component |
Technology |
| Protocol |
OpenTelemetry (traces, metrics, logs) |
| Query Engine |
DataFusion (PostgreSQL-compatible SQL) |
| Python SDK |
Python 3.9+ with async support |
| JS/TS SDK |
Node.js, browsers, Next.js, Cloudflare, Deno |
| Rust SDK |
Native Rust implementation |
| MCP Server |
logfire-mcp PyPI package |
Architectural Layers
Application Code
|
Logfire SDK (logfire.configure() + instrument_*)
|
OpenTelemetry Exporters
|
Logfire Backend (Cloud)
|
DataFusion SQL Engine -> MCP Server -> AI Agents
Data Model
- Spans: Operations with duration, parent/child relationships
- Traces: Tree structures of related spans
- Metrics: Aggregated values over time (histograms, counters)
- Logs: Timestamped events without duration
MCP Server Tools
find_exceptions(age: int) - Get exception counts grouped by file
find_exceptions_in_file(filepath: str, age: int) - Detailed trace info for file
arbitrary_query(query: str, age: int) - Custom SQL queries on traces/metrics
get_logfire_records_schema() - Schema for custom queries
Installation and Usage
Installation
# Basic installation
pip install logfire
# Using uv
uv pip install logfire
# MCP server
pip install logfire-mcp
# or run directly
uvx logfire-mcp@latest
Authentication
logfire auth
Basic Instrumentation
import logfire
logfire.configure()
logfire.info('Hello, {name}!', name='world')
# Manual spans
with logfire.span('Processing {item}', item='data'):
# ... processing code ...
logfire.debug('Step completed')
OpenAI Instrumentation
import openai
import logfire
client = openai.Client()
logfire.configure()
logfire.instrument_openai()
response = client.chat.completions.create(
model='gpt-4',
messages=[{'role': 'user', 'content': 'Hello!'}],
)
Anthropic Instrumentation
import anthropic
import logfire
client = anthropic.Anthropic()
logfire.configure()
logfire.instrument_anthropic()
response = client.messages.create(
max_tokens=1000,
model='claude-3-haiku-20240307',
system='You are a helpful assistant.',
messages=[{'role': 'user', 'content': 'Hello!'}],
)
FastAPI + Database Example
from fastapi import FastAPI
import logfire
app = FastAPI()
logfire.configure()
logfire.instrument_fastapi(app)
logfire.instrument_httpx()
logfire.instrument_sqlalchemy()
Pydantic AI Integration
from pydantic_ai import Agent
import logfire
logfire.configure()
logfire.instrument_pydantic_ai()
agent = Agent('openai:gpt-4', system_prompt='You are helpful.')
result = agent.run_sync('Hello!')
MCP Server Configuration (Claude Code)
claude mcp add logfire -e LOGFIRE_READ_TOKEN="your-token" -- uvx logfire-mcp@latest
SQL Query Example
SELECT
span_name,
attributes->>'gen_ai.usage.input_tokens' as input_tokens,
attributes->>'gen_ai.usage.output_tokens' as output_tokens,
duration
FROM records
WHERE span_name LIKE 'llm%'
ORDER BY start_timestamp DESC
LIMIT 100
Relevance to Claude Code Development
Direct Applications
Agent Debugging: Logfire's full-stack tracing reveals both AI reasoning and backend behavior when agents call tools, enabling diagnosis of whether issues are in prompts or infrastructure.
MCP Server for AI Self-Debugging: The Logfire MCP server allows Claude Code to query its own production traces via SQL, enabling self-diagnosis of errors and performance issues.
Claude Agent SDK Support: Native instrumentation for Claude Agent SDK via Langsmith OTel bridge provides visibility into Claude-based agent systems.
Pydantic AI Integration: First-class support for Pydantic AI (used in many Claude Code skills) with automatic conversation tracing.
Evaluation Pipeline: Integration with pydantic-evals provides code-first, version-controlled evaluation framework for testing agent behaviors.
Patterns Worth Adopting
Full-Stack Context for AI: Logfire's approach of combining AI observability with backend tracing ensures debugging includes the complete picture (the "Scenario A vs B" diagnostic pattern).
SQL-Queryable Telemetry: Exposing observability data via SQL enables both human analysis and AI-powered querying - a pattern applicable to other debugging tools.
Code-First Evaluations: pydantic-evals treats evaluations as code (version-controlled, CI-integrated) rather than UI-managed, a pattern for rigorous testing.
MCP-Enabled Observability: Providing MCP server access to telemetry data enables AI agents to autonomously investigate production issues.
Progressive Instrumentation: One-line instrument_*() calls provide immediate value with minimal code changes - a pattern for tool adoption.
Integration Opportunities
Session Debugging: Add Logfire instrumentation to Claude Code skills/agents for production debugging.
Self-Healing Agents: Use Logfire MCP to enable agents to detect and diagnose their own failures.
Cost Tracking: Monitor token usage across different agent configurations to optimize costs.
Performance Baselines: Establish latency and throughput baselines for agent operations.
Evaluation Framework: Adopt pydantic-evals patterns for systematic skill/agent testing.
Comparison with AI-Only Tools
| Aspect |
Logfire |
Langfuse/Arize/LangSmith |
| Primary Focus |
Full-stack AI observability |
LLM-only observability |
| Backend Visibility |
Yes (via OpenTelemetry) |
No (tool call input/output only) |
| Query Interface |
PostgreSQL-compatible SQL |
Proprietary APIs/UI |
| AI Agent Queryable |
Yes (MCP server with SQL) |
Limited to predefined endpoints |
| Protocol |
OpenTelemetry standard |
Proprietary |
| Lock-in |
None (OTel portable) |
Vendor-specific |
| Pydantic Integration |
Native (same team) |
External integration |
Pricing
| Tier |
Price |
Retention |
Notes |
| Free |
$0 (first 10M units/month) |
30 days |
Equivalent to $20 of usage |
| Pro |
$2 per million units |
30 days |
Spans, logs, or metrics metered |
| Enterprise |
Contact sales |
Extended |
Custom retention, self-hosting |
- Unit: One span, log, or metric
- Payload: 5 KB average per unit (generous)
- No: Per-host, per-seat, or per-project charges
References
Research Method: Information gathered from official GitHub repository README, GitHub API (stars, forks, description, topics), PyPI package metadata, and official documentation markdown files fetched directly from GitHub. Statistics verified via direct API calls on 2026-02-05.
Freshness Tracking
| Field |
Value |
| Version Documented |
4.22.0 |
| Release Date |
2026-02-04 |
| GitHub Stars |
3,984 (as of 2026-02-05) |
| Next Review Date |
2026-05-05 |
Review Triggers:
- Major version release (5.x)
- Significant new LLM framework integrations
- MCP server feature additions
- pydantic-evals major updates
- GitHub stars milestone (5K, 10K)
- New AI-specific dashboard features
- Claude Code native integration announcements
1---2name: pydantic-logfire3description: Pydantic Logfire is an AI-native observability platform built by the team behind Pydantic.4---5# Pydantic Logfire67| Field | Value |8| ------------- | ------------------------------------------------------------------------- |9| Research Date | 2026-02-05 |10| Primary URL | <https://logfire.pydantic.dev/docs/> |11| GitHub | <https://github.com/pydantic/logfire> |12| PyPI | <https://pypi.org/project/logfire/> |13| Version | 4.22.0 (released 2026-02-04) |14| License | MIT |15| Slack | <https://logfire.pydantic.dev/docs/join-slack/> |16| Managed | <https://logfire.pydantic.dev/> (Pydantic - cloud platform) |17| MCP Server | <https://github.com/pydantic/logfire-mcp> |1819---2021## Overview2223Pydantic Logfire is an AI-native observability platform built by the team behind Pydantic. It provides full-stack tracing for LLM applications using OpenTelemetry, combining AI-specific features (conversation panels, token tracking, cost monitoring, tool call inspection) with traditional application observability. Unlike AI-only observability tools that only see the LLM layer, Logfire traces the entire application stack, enabling debugging of both AI reasoning and backend infrastructure issues.2425---2627## Problem Addressed2829| Problem | Solution |30| ---------------------------------------------------- | ------------------------------------------------------------------------------- |31| AI-only tools miss backend context | Full-stack OpenTelemetry tracing shows what happened inside tool calls |32| Debugging LLM conversations is difficult | Human-readable conversation panels with tool call inspection |33| Token usage and costs are opaque | Built-in token tracking and cost monitoring across providers |34| Observability tools have proprietary query languages | SQL-based analysis (PostgreSQL-compatible) queryable by AI agents |35| Existing tools cannot be queried by AI | MCP server provides SQL access for AI agents to query production data |36| Pydantic validation errors are hard to trace | Native Pydantic integration with validation analytics |37| Agent debugging requires multiple tools | Single platform for traces, metrics, logs with agent-specific visualization |38| Streaming responses are hard to observe | Full visibility into streamed chunks with dedicated span handling |39| Evaluations are UI-managed in other tools | Code-first evaluations via pydantic-evals, version-controlled and CI-integrated |40| Lock-in with proprietary instrumentation | Built on OpenTelemetry standard, data portable to any OTel backend |4142---4344## Key Statistics4546| Metric | Value | Date Gathered |47| ---------------- | ------------ | ------------- |48| GitHub Stars | 3,984 | 2026-02-05 |49| GitHub Forks | 204 | 2026-02-05 |50| Open Issues | N/A | 2026-02-05 |51| Primary Language | Python | 2026-02-05 |52| Python Requires | >=3.9 | 2026-02-05 |53| Repository Age | Since April 2024 | 2026-02-05 |5455---5657## Key Features5859### AI/LLM Observability6061- **LLM Panels**: Visual inspection of conversations, tool calls, and responses62- **Token Tracking**: Per-request and per-model token usage visibility63- **Cost Monitoring**: Spending tracking across providers with threshold alerts64- **Tool Call Inspection**: Arguments, responses, and latency for each tool call65- **Streaming Support**: Debug streaming responses with chunk-level visibility66- **Multi-turn Conversations**: Trace entire conversation flows across turns6768### LLM Framework Integrations6970| Framework | Integration Method |71| --------------- | ------------------------------------------- |72| Pydantic AI | `logfire.instrument_pydantic_ai()` |73| OpenAI | `logfire.instrument_openai()` |74| OpenAI Agents | `logfire.instrument_openai_agents()` |75| Anthropic | `logfire.instrument_anthropic()` |76| Claude Agent SDK| Via Langsmith OTel bridge |77| LangChain | Built-in OTel support |78| LlamaIndex | `logfire.instrument_llamaindex()` |79| LiteLLM | `logfire.instrument_litellm()` |80| Google GenAI | `logfire.instrument_google_genai()` |81| Magentic | Built-in Logfire support |82| Mirascope | `@with_logfire` decorator |8384### Web Framework Integrations8586- **FastAPI**: `logfire.instrument_fastapi()`87- **Django**: `logfire.instrument_django()`88- **Flask**: `logfire.instrument_flask()`89- **Starlette**: `logfire.instrument_starlette()`90- **AIOHTTP**: `logfire.instrument_aiohttp_client()`, `logfire.instrument_aiohttp_server()`91- **ASGI/WSGI**: Generic middleware support9293### Database Integrations9495- **Psycopg**: `logfire.instrument_psycopg()`96- **SQLAlchemy**: `logfire.instrument_sqlalchemy()`97- **Asyncpg**: `logfire.instrument_asyncpg()`98- **PyMongo**: `logfire.instrument_pymongo()`99- **MySQL**: `logfire.instrument_mysql()`100- **SQLite3**: `logfire.instrument_sqlite3()`101- **Redis**: `logfire.instrument_redis()`102- **BigQuery**: Built-in, no config needed103104### HTTP Client Integrations105106- **HTTPX**: `logfire.instrument_httpx()`107- **Requests**: `logfire.instrument_requests()`108- **AIOHTTP**: `logfire.instrument_aiohttp_client()`109110### Additional Integrations111112- **AWS Lambda**: `logfire.instrument_aws_lambda()`113- **Celery**: `logfire.instrument_celery()`114- **Airflow**: Built-in, config needed115- **FastStream**: Built-in, config needed116- **Pytest**: `pytest --logfire` plugin117- **Standard Logging**: Integration with logging, loguru, structlog118- **System Metrics**: `logfire.instrument_system_metrics()`119- **Stripe**: Via HTTP instrumentation120121### Platform Features122123- **SQL Query Interface**: PostgreSQL-compatible SQL for data analysis124- **MCP Server**: Native Model Context Protocol server for AI agent querying125- **Live View**: Real-time trace visualization dashboard126- **Natural Language Search**: LLM-powered SQL generation via Pydantic AI127- **Standard Dashboards**: Pre-built dashboards for web server metrics, system metrics128- **Evaluations**: Integration with pydantic-evals for code-first testing129130---131132## Technical Architecture133134### Stack Components135136| Component | Technology |137| --------------- | --------------------------------------------- |138| Protocol | OpenTelemetry (traces, metrics, logs) |139| Query Engine | DataFusion (PostgreSQL-compatible SQL) |140| Python SDK | Python 3.9+ with async support |141| JS/TS SDK | Node.js, browsers, Next.js, Cloudflare, Deno |142| Rust SDK | Native Rust implementation |143| MCP Server | logfire-mcp PyPI package |144145### Architectural Layers146147```text148Application Code149 |150Logfire SDK (logfire.configure() + instrument_*)151 |152OpenTelemetry Exporters153 |154Logfire Backend (Cloud)155 |156DataFusion SQL Engine -> MCP Server -> AI Agents157```158159### Data Model160161- **Spans**: Operations with duration, parent/child relationships162- **Traces**: Tree structures of related spans163- **Metrics**: Aggregated values over time (histograms, counters)164- **Logs**: Timestamped events without duration165166### MCP Server Tools1671681. `find_exceptions(age: int)` - Get exception counts grouped by file1692. `find_exceptions_in_file(filepath: str, age: int)` - Detailed trace info for file1703. `arbitrary_query(query: str, age: int)` - Custom SQL queries on traces/metrics1714. `get_logfire_records_schema()` - Schema for custom queries172173---174175## Installation and Usage176177### Installation178179```bash180# Basic installation181pip install logfire182183# Using uv184uv pip install logfire185186# MCP server187pip install logfire-mcp188# or run directly189uvx logfire-mcp@latest190```191192### Authentication193194```bash195logfire auth196```197198### Basic Instrumentation199200```python201import logfire202203logfire.configure()204logfire.info('Hello, {name}!', name='world')205206# Manual spans207with logfire.span('Processing {item}', item='data'):208 # ... processing code ...209 logfire.debug('Step completed')210```211212### OpenAI Instrumentation213214```python215import openai216import logfire217218client = openai.Client()219logfire.configure()220logfire.instrument_openai()221222response = client.chat.completions.create(223 model='gpt-4',224 messages=[{'role': 'user', 'content': 'Hello!'}],225)226```227228### Anthropic Instrumentation229230```python231import anthropic232import logfire233234client = anthropic.Anthropic()235logfire.configure()236logfire.instrument_anthropic()237238response = client.messages.create(239 max_tokens=1000,240 model='claude-3-haiku-20240307',241 system='You are a helpful assistant.',242 messages=[{'role': 'user', 'content': 'Hello!'}],243)244```245246### FastAPI + Database Example247248```python249from fastapi import FastAPI250import logfire251252app = FastAPI()253254logfire.configure()255logfire.instrument_fastapi(app)256logfire.instrument_httpx()257logfire.instrument_sqlalchemy()258```259260### Pydantic AI Integration261262```python263from pydantic_ai import Agent264import logfire265266logfire.configure()267logfire.instrument_pydantic_ai()268269agent = Agent('openai:gpt-4', system_prompt='You are helpful.')270result = agent.run_sync('Hello!')271```272273### MCP Server Configuration (Claude Code)274275```bash276claude mcp add logfire -e LOGFIRE_READ_TOKEN="your-token" -- uvx logfire-mcp@latest277```278279### SQL Query Example280281```sql282SELECT283 span_name,284 attributes->>'gen_ai.usage.input_tokens' as input_tokens,285 attributes->>'gen_ai.usage.output_tokens' as output_tokens,286 duration287FROM records288WHERE span_name LIKE 'llm%'289ORDER BY start_timestamp DESC290LIMIT 100291```292293---294295## Relevance to Claude Code Development296297### Direct Applications2982991. **Agent Debugging**: Logfire's full-stack tracing reveals both AI reasoning and backend behavior when agents call tools, enabling diagnosis of whether issues are in prompts or infrastructure.3003012. **MCP Server for AI Self-Debugging**: The Logfire MCP server allows Claude Code to query its own production traces via SQL, enabling self-diagnosis of errors and performance issues.3023033. **Claude Agent SDK Support**: Native instrumentation for Claude Agent SDK via Langsmith OTel bridge provides visibility into Claude-based agent systems.3043054. **Pydantic AI Integration**: First-class support for Pydantic AI (used in many Claude Code skills) with automatic conversation tracing.3063075. **Evaluation Pipeline**: Integration with pydantic-evals provides code-first, version-controlled evaluation framework for testing agent behaviors.308309### Patterns Worth Adopting3103111. **Full-Stack Context for AI**: Logfire's approach of combining AI observability with backend tracing ensures debugging includes the complete picture (the "Scenario A vs B" diagnostic pattern).3123132. **SQL-Queryable Telemetry**: Exposing observability data via SQL enables both human analysis and AI-powered querying - a pattern applicable to other debugging tools.3143153. **Code-First Evaluations**: pydantic-evals treats evaluations as code (version-controlled, CI-integrated) rather than UI-managed, a pattern for rigorous testing.3163174. **MCP-Enabled Observability**: Providing MCP server access to telemetry data enables AI agents to autonomously investigate production issues.3183195. **Progressive Instrumentation**: One-line `instrument_*()` calls provide immediate value with minimal code changes - a pattern for tool adoption.320321### Integration Opportunities3223231. **Session Debugging**: Add Logfire instrumentation to Claude Code skills/agents for production debugging.3243252. **Self-Healing Agents**: Use Logfire MCP to enable agents to detect and diagnose their own failures.3263273. **Cost Tracking**: Monitor token usage across different agent configurations to optimize costs.3283294. **Performance Baselines**: Establish latency and throughput baselines for agent operations.3303315. **Evaluation Framework**: Adopt pydantic-evals patterns for systematic skill/agent testing.332333### Comparison with AI-Only Tools334335| Aspect | Logfire | Langfuse/Arize/LangSmith |336| ----------------------- | ------------------------------------ | ------------------------------- |337| Primary Focus | Full-stack AI observability | LLM-only observability |338| Backend Visibility | Yes (via OpenTelemetry) | No (tool call input/output only)|339| Query Interface | PostgreSQL-compatible SQL | Proprietary APIs/UI |340| AI Agent Queryable | Yes (MCP server with SQL) | Limited to predefined endpoints |341| Protocol | OpenTelemetry standard | Proprietary |342| Lock-in | None (OTel portable) | Vendor-specific |343| Pydantic Integration | Native (same team) | External integration |344345---346347## Pricing348349| Tier | Price | Retention | Notes |350| ----------- | ------------------------------- | --------- | ------------------------------------ |351| Free | $0 (first 10M units/month) | 30 days | Equivalent to $20 of usage |352| Pro | $2 per million units | 30 days | Spans, logs, or metrics metered |353| Enterprise | Contact sales | Extended | Custom retention, self-hosting |354355- **Unit**: One span, log, or metric356- **Payload**: 5 KB average per unit (generous)357- **No**: Per-host, per-seat, or per-project charges358359---360361## References362363| Source | URL | Accessed |364| ---------------------------- | -------------------------------------------------------------------------- | ---------- |365| Official Documentation | <https://logfire.pydantic.dev/docs/> | 2026-02-05 |366| GitHub Repository | <https://github.com/pydantic/logfire> | 2026-02-05 |367| GitHub README | <https://raw.githubusercontent.com/pydantic/logfire/main/README.md> | 2026-02-05 |368| PyPI Package | <https://pypi.org/project/logfire/> | 2026-02-05 |369| AI Observability Guide | <https://logfire.pydantic.dev/docs/ai-observability/> | 2026-02-05 |370| Integrations Index | <https://logfire.pydantic.dev/docs/integrations/> | 2026-02-05 |371| OpenAI Integration | <https://logfire.pydantic.dev/docs/integrations/llms/openai/> | 2026-02-05 |372| Anthropic Integration | <https://logfire.pydantic.dev/docs/integrations/llms/anthropic/> | 2026-02-05 |373| Claude Agent SDK Integration | <https://logfire.pydantic.dev/docs/integrations/llms/claude-agent-sdk/> | 2026-02-05 |374| Pydantic AI Integration | <https://logfire.pydantic.dev/docs/integrations/llms/pydanticai/> | 2026-02-05 |375| MCP Server Guide | <https://logfire.pydantic.dev/docs/how-to-guides/mcp-server/> | 2026-02-05 |376| MCP Server Repository | <https://github.com/pydantic/logfire-mcp> | 2026-02-05 |377| Concepts Documentation | <https://logfire.pydantic.dev/docs/concepts/> | 2026-02-05 |378| Pricing/Costs | <https://logfire.pydantic.dev/docs/logfire-costs/> | 2026-02-05 |379380**Research Method**: Information gathered from official GitHub repository README, GitHub API (stars, forks, description, topics), PyPI package metadata, and official documentation markdown files fetched directly from GitHub. Statistics verified via direct API calls on 2026-02-05.381382---383384## Freshness Tracking385386| Field | Value |387| ------------------ | ----------------------------------- |388| Version Documented | 4.22.0 |389| Release Date | 2026-02-04 |390| GitHub Stars | 3,984 (as of 2026-02-05) |391| Next Review Date | 2026-05-05 |392393**Review Triggers**:394395- Major version release (5.x)396- Significant new LLM framework integrations397- MCP server feature additions398- pydantic-evals major updates399- GitHub stars milestone (5K, 10K)400- New AI-specific dashboard features401- Claude Code native integration announcements