Log inSubmit server
Logfire MCP logo

Logfire MCP

by pydantic

Archived STDIO MCP server for accessing OpenTelemetry traces and metrics through Logfire.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Logfire MCP

Pick your client, then add it in one click or paste the config.

Streamable HTTP (Remote)
Server URL
https://logfire-eu.pydantic.dev/mcp

Remote servers are added in the app, not the config file: Customize → Connectors → Add custom connector, then paste this URL.

Hosted endpointLive · TodayLive Remote EndpointOur automated health check connected to this remote MCP endpoint successfully.Last checked 10/26/2026, 8:15:32 PM

Clients with native remote MCP support can connect directly to this URL.

Remote endpoint
https://logfire-eu.pydantic.dev/mcp

Overview

pydantic/logfire-mcp MCP server exposes access to OpenTelemetry traces and metrics through Logfire. It uses an MCP STDIO implementation, but the repository is archived and this implementation is no longer updated. Consider it only when evaluating the older local server; Logfire now provides a remote MCP server for continued development.

Use cases

  • Inspect OpenTelemetry traces through Logfire
  • Review OpenTelemetry metrics through Logfire
  • Evaluate an existing STDIO-based MCP setup
  • Compare the archived local server with Logfire’s remote MCP server

Key features

  • Access OpenTelemetry traces through Logfire
  • Access OpenTelemetry metrics through Logfire
  • Expose Logfire observability data over MCP
  • Use the archived STDIO implementation

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

16/19 checks healthy over the last 78d

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars162Stargazers on the source repository.
Last commit3mo agoMost recent push to the default branch.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How Logfire MCP works

What pydantic/logfire-mcp MCP server does

The pydantic/logfire-mcp MCP server gives MCP clients access to observability data held in Logfire. Its documented scope is OpenTelemetry traces and metrics, allowing an MCP-connected application to work with those data types through Logfire rather than accessing them through a separate interface.

The repository is focused on the local STDIO implementation.

How it works

The pydantic/logfire-mcp MCP server communicates through the MCP STDIO transport. An MCP client starts or connects to the local process, and the process provides access to Logfire’s OpenTelemetry traces and metrics within that MCP session.

The repository itself does not document a hosted endpoint, authentication flow, configuration keys, installation command, or client-specific setup. Those details should not be inferred from the repository description. The README instead directs users to Logfire’s MCP server documentation for additional information.

This design is relevant for clients that can use an MCP server over STDIO.

Limitations and notes

The pydantic/logfire-mcp MCP server repository is archived. Its README explicitly says that the STDIO server is no longer being updated. That status matters when choosing it for a new deployment: future tool changes, fixes, or improvements should not be expected from this repository.

Logfire now provides a remote MCP server, according to the repository notice. The notice says the remote server enables faster iteration and a better experience, but it does not provide its endpoint, setup procedure, authentication requirements, or a complete list of tools. Use the linked documentation to evaluate that alternative.

Those fields should be treated as unspecified rather than assumed. This listing therefore best fits research into the archived local implementation or existing environments that already depend on it, not a general recommendation for new integrations.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Logfire MCP

pydantic/logfire-mcp is an MCP server that connects an MCP client to Logfire for access to OpenTelemetry traces and metrics. Its main capabilities cover those two observability data types. The repository contains a STDIO implementation, but it is archived and no longer updated; Logfire now offers a remote MCP server.

It identifies the repository as a STDIO MCP server and directs users to Logfire’s MCP server documentation for further guidance. Because the repository is archived, evaluate the documented remote MCP server before starting a new setup.

The repository describes a server using MCP over STDIO, but it does not name supported clients or provide Cursor configuration. Confirm support and the required client setup in the Logfire documentation.

No, the repository’s STDIO MCP server is archived and no longer being updated.

Related MCP servers

All in Monitoring All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewLogfire MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/pydantic-logfire-mcp?style=directory)](https://allmcps.com/mcp/pydantic-logfire-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/pydantic-logfire-mcp"><img src="https://allmcps.com/api/badge/pydantic-logfire-mcp?style=directory" alt="Logfire MCP on AllMCPs" /></a>