OBSERVABILITY / Pydantic
Logfire MCP
Connects assistants to Logfire traces, metrics and observability management tools in the chosen region.
“Pydantic Logfire provides a hosted remote MCP server that you can use without installing anything locally.”
01 / THE REASONING
Why this made the selection.
- Provides region-specific hosted endpoints with browser-based account authorization.
- Documents telemetry queries, management tools and organization controls for restricting the available tool surface.
- Pydantic’s current guide describes a remote Logfire MCP server with a daily query budget and an option to limit external clients to read-only tools.
- The GitHub page listed on this row says the older stdio repository is archived and is no longer being updated.
02 / THE REVIEW RECORD
What we actually inspected.
Source review has boundaries.
A clear record is more useful than a “safe” badge.
Material inspected
- Current hosted-server guide, regional endpoints, authentication, tool permissions and query-budget sections
- Archive notice in the previous standalone repository
- https://pydantic.dev/docs/logfire/guides/mcp-server/
- https://github.com/pydantic/logfire-mcp
- Round 2 reread of acquired publisher setup and permission evidence; see immutable wave review.
Our findings
- The current guide distinguishes hosted regional setup from the older local server and warns that telemetry is untrusted input.
- The Logfire guide says there is a concurrency limit and a daily query budget per organization. After the budget is spent, MCP queries are refused until it refills, and that refusal does not stop web UI or read-token queries.
- The same guide links a control to limit every external MCP client to read-only tools.
- The listed GitHub repository says it is archived, that the stdio server in the package is no longer updated, and that a remote MCP server is the current direction.
- The plugin defaults to the US endpoint; organization administrators can restrict external MCP clients to read-only tools and control feedback sharing.
Not established by this review
- No MCP server or upstream package was installed or run.
- No authenticated account, client handshake, query, write operation or security test was performed.
- The resource was not executed and its tools were not called.
- The server was not called. A source review is not a runtime or security certification.
The review applies to the material and revision named here. A newer upstream release can change its behavior.
03 / PUT IT TO WORK
Connect a server deliberately.
- Use https://logfire-us.pydantic.dev/mcp for US projects or https://logfire-eu.pydantic.dev/mcp for EU projects.
- Add the URL as a remote MCP server and complete browser authorization for the intended organization.
- Review exposed tools and organizational restrictions before querying sensitive telemetry or making changes.
Before you start
- A Logfire account with access to the target organization and project
- An OAuth-capable remote MCP client
Documented configuration example
Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.
{
"mcpServers": {
"logfire": {
"url": "https://logfire-us.pydantic.dev/mcp"
}
}
}04 / FOLLOW THE EVIDENCE
The source trail.
Our notes are separate from the original resource.
Check upstream before adopting a new version.
https://pydantic.dev/docs/logfire/guides/mcp-server/
Supports: summary, upstreamDescription, whySelected, bestFor, install, compatibility, transports, limitations, access, review
https://github.com/pydantic/logfire-mcp
Supports: limitations, review