From 58264deb628472e8eea35422fc3f035fe9603d54 Mon Sep 17 00:00:00 2001 From: Hasan Ramezani Date: Mon, 9 Feb 2026 15:12:10 +0100 Subject: [PATCH 1/3] docs: add remote MCP server section to README Add documentation for the hosted remote MCP server as the recommended way to use Logfire MCP. This provides an easier setup experience for users who don't need to run the server locally. - Add Remote MCP Server section at the top of README - Include separate configs for US and EU regions - Add region hints to help users choose the correct endpoint - Reorganize local setup under "Running Locally" section Co-Authored-By: Claude Opus 4.5 --- README.md | 51 +++++++++++++++++++++++++++++++++++++----- tests/README.md.jinja | 52 +++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 97 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index a7b8867..d5b2d72 100644 --- a/README.md +++ b/README.md @@ -1,9 +1,48 @@ - - # Pydantic Logfire MCP Server -This repository contains a Model Context Protocol (MCP) server with tools that can access the OpenTelemetry traces and -metrics you've sent to Pydantic Logfire. +## Remote MCP Server (Recommended) + +Pydantic Logfire provides a hosted remote MCP server that you can use instead of running this package locally. +This is the easiest way to get started with the Logfire MCP server. + +To use the remote MCP server, add the following configuration to your MCP client. + +**Choose the endpoint that matches your Logfire data region:** + +For **US region** (`logfire.pydantic.dev`): +```json +{ + "mcpServers": { + "logfire": { + "type": "http", + "url": "https://logfire-us.pydantic.dev/mcp" + } + } +} +``` + +For **EU region** (`logfire-eu.pydantic.dev`): +```json +{ + "mcpServers": { + "logfire": { + "type": "http", + "url": "https://logfire-eu.pydantic.dev/mcp" + } + } +} +``` + +> [!NOTE] +> The remote MCP server handles authentication automatically through your browser. When you first connect, +> you'll be prompted to authenticate with your Pydantic Logfire account. + +--- + +## Running Locally + +If you prefer to run the MCP server locally (for example, for offline use or custom configurations), +you can use this package instead. Pydantic Logfire Server MCP server @@ -17,12 +56,12 @@ traces, and make use of the results of arbitrary SQL queries executed using the * `find_exceptions_in_file` - Get the details about the 10 most recent exceptions on the file. * Arguments: * `filepath` (string) - The path to the file to find exceptions in. - * `age` (integer) - Number of minutes to look back, e.g. 30 for last 30 minutes. Maximum allowed value is 7 days. + * `age` (integer) - Number of minutes to look back, e.g. 30 for last 30 minutes. Maximum allowed value is 30 days. * `arbitrary_query` - Run an arbitrary query on the Pydantic Logfire database. * Arguments: * `query` (string) - The query to run, as a SQL string. - * `age` (integer) - Number of minutes to look back, e.g. 30 for last 30 minutes. Maximum allowed value is 7 days. + * `age` (integer) - Number of minutes to look back, e.g. 30 for last 30 minutes. Maximum allowed value is 30 days. * `logfire_link` - Creates a link to help the user to view the trace in the Logfire UI. * Arguments: diff --git a/tests/README.md.jinja b/tests/README.md.jinja index 7de4079..68d6eec 100644 --- a/tests/README.md.jinja +++ b/tests/README.md.jinja @@ -3,6 +3,58 @@ This repository contains a Model Context Protocol (MCP) server with tools that can access the OpenTelemetry traces and metrics you've sent to Pydantic Logfire. +## Remote MCP Server (Recommended) + +Pydantic Logfire provides a hosted remote MCP server that you can use instead of running this package locally. +This is the easiest way to get started with the Logfire MCP server. + +To use the remote MCP server, add the following configuration to your MCP client. + +**Choose the endpoint that matches your Logfire data region:** + +For **US region** (`logfire-us.pydantic.dev`): +```json +{ + "mcpServers": { + "logfire": { + "type": "http", + "url": "https://logfire-us.pydantic.dev/mcp" + } + } +} +``` + +For **EU region** (`logfire-eu.pydantic.dev`): +```json +{ + "mcpServers": { + "logfire": { + "type": "http", + "url": "https://logfire-eu.pydantic.dev/mcp" + } + } +} +``` + +> [!NOTE] +> The remote MCP server handles authentication automatically through your browser. When you first connect, +> you'll be prompted to authenticate with your Pydantic Logfire account. + +> [!NOTE] +> If you are running a self-hosted Logfire instance, you should use the [Running Locally](#running-locally) section below +> to configure the MCP server with your custom base URL. + +--- + +## Running Locally (Deprecated) + +> [!WARNING] +> Running the MCP server locally is deprecated. Please use the [Remote MCP Server](#remote-mcp-server-recommended) instead. +> The local server will continue to work, but we recommend migrating to the remote server for a better experience. + +If you prefer to run the MCP server locally (for example, for self-hosted Logfire or custom configurations), +you can use this package instead. + Pydantic Logfire Server MCP server From c30fac0709a36f932828dba8f10e267165f052a2 Mon Sep 17 00:00:00 2001 From: Hasan Ramezani Date: Tue, 10 Feb 2026 09:50:37 +0100 Subject: [PATCH 2/3] fix --- README.md | 17 ++++++++++++++--- 1 file changed, 14 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index d5b2d72..3761b99 100644 --- a/README.md +++ b/README.md @@ -1,5 +1,8 @@ # Pydantic Logfire MCP Server +This repository contains a Model Context Protocol (MCP) server with tools that can access the OpenTelemetry traces and +metrics you've sent to Pydantic Logfire. + ## Remote MCP Server (Recommended) Pydantic Logfire provides a hosted remote MCP server that you can use instead of running this package locally. @@ -9,7 +12,7 @@ To use the remote MCP server, add the following configuration to your MCP client **Choose the endpoint that matches your Logfire data region:** -For **US region** (`logfire.pydantic.dev`): +For **US region** (`logfire-us.pydantic.dev`): ```json { "mcpServers": { @@ -37,11 +40,19 @@ For **EU region** (`logfire-eu.pydantic.dev`): > The remote MCP server handles authentication automatically through your browser. When you first connect, > you'll be prompted to authenticate with your Pydantic Logfire account. +> [!NOTE] +> If you are running a self-hosted Logfire instance, you should use the [Running Locally](#running-locally) section below +> to configure the MCP server with your custom base URL. + --- -## Running Locally +## Running Locally (Deprecated) + +> [!WARNING] +> Running the MCP server locally is deprecated. Please use the [Remote MCP Server](#remote-mcp-server-recommended) instead. +> The local server will continue to work, but we recommend migrating to the remote server for a better experience. -If you prefer to run the MCP server locally (for example, for offline use or custom configurations), +If you prefer to run the MCP server locally (for example, for self-hosted Logfire or custom configurations), you can use this package instead. From 59d7040b82e56726d2962b3562d1b5715a20eb8b Mon Sep 17 00:00:00 2001 From: Hasan Ramezani Date: Tue, 10 Feb 2026 13:06:02 +0100 Subject: [PATCH 3/3] Fix self-hosted MCP docs to reference remote server URL Self-hosted customers have the MCP server in their own deployment, so they should use their instance URL rather than running locally. Co-Authored-By: Claude Opus 4.6 --- tests/README.md.jinja | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/tests/README.md.jinja b/tests/README.md.jinja index 68d6eec..1a9677e 100644 --- a/tests/README.md.jinja +++ b/tests/README.md.jinja @@ -41,8 +41,8 @@ For **EU region** (`logfire-eu.pydantic.dev`): > you'll be prompted to authenticate with your Pydantic Logfire account. > [!NOTE] -> If you are running a self-hosted Logfire instance, you should use the [Running Locally](#running-locally) section below -> to configure the MCP server with your custom base URL. +> If you are running a self-hosted Logfire instance, replace the URL above with your own Logfire instance URL +> (e.g., `https://logfire.my-company.com/mcp`), as the remote MCP server is hosted alongside your Logfire deployment. ---