Pydantic Logfire MCP server

Hosted remote MCP server for Logfire's OpenTelemetry-native observability platform, exposing SQL queries over traces and metrics plus management of dashboards, alerts, notification channels, issues, and feature-flag variables. A separate EU endpoint exists at logfire-eu.pydantic.dev/mcp; OAuth browser login is standard, with API-key Bearer auth for sandboxed environments.

Endpoint and access

OAuth sign-in: the first time you connect, your client opens the vendor's own authorization prompt in a browser.

OAuth sign-inEndpoint checked 2026-10-05Operated by Pydantic Services Inc.

MCP endpoint (Streamable HTTP)

https://logfire-us.pydantic.dev/mcp

Vendor documentation

What you can do with it

Query OpenTelemetry traces and metrics with SQL to debug application issues.
Find recent exceptions in a file and inspect distributed traces.
Create and manage dashboards, panels, and SQL-based alerts.
Triage tracked exception issues and manage notification channels.
Use the EU endpoint for EU data regions.

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http pydantic-logfire https://logfire-us.pydantic.dev/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add pydantic-logfire --url https://logfire-us.pydantic.dev/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable pydantic-logfire in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "pydantic-logfire": {
      "url": "https://logfire-us.pydantic.dev/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "pydantic-logfire": {
      "type": "streamableHttp",
      "url": "https://logfire-us.pydantic.dev/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start pydantic-logfire and inspect its tools.

VS Code configuration

{
  "servers": {
    "pydantic-logfire": {
      "type": "http",
      "url": "https://logfire-us.pydantic.dev/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http pydantic-logfire https://logfire-us.pydantic.dev/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "pydantic-logfire": {
      "url": "https://logfire-us.pydantic.dev/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "pydantic-logfire": {
      "serverUrl": "https://logfire-us.pydantic.dev/mcp"
    }
  }
}

See all 1,583

Do you run Pydantic Logfire?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing