This repository was archived by the owner on Mar 24, 2026. It is now read-only.
docs: add remote MCP server section to README#52
Merged
Conversation
hramezani
commented
Feb 9, 2026
Kludex
reviewed
Feb 10, 2026
| @@ -1,7 +1,48 @@ | |||
| # Pydantic Logfire MCP Server | |||
|
|
|||
| This repository contains a Model Context Protocol (MCP) server with tools that can access the OpenTelemetry traces and | |||
Member
There was a problem hiding this comment.
We should have text between heading sections.
Kludex
reviewed
Feb 10, 2026
|
|
||
| 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) |
Member
There was a problem hiding this comment.
We should have a note about self hosted.
Kludex
reviewed
Feb 10, 2026
Comment on lines
+42
to
+45
| ## 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. |
Member
There was a problem hiding this comment.
We should set a warning and say that it's deprecated.
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 <noreply@anthropic.com>
hramezani
force-pushed
the
hramezani/add-remote-mcp-docs
branch
from
65ca314 to
58264de
Compare
Kludex
reviewed
Feb 10, 2026
Comment on lines
+43
to
+45
| > [!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. |
Member
There was a problem hiding this comment.
That's not what I mean... It should be possible to use the above on self hosted, isn't it not?
Member
Author
There was a problem hiding this comment.
If we include it in helm chart, they can use it
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 <noreply@anthropic.com>
Kludex
approved these changes
Feb 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
logfire.pydantic.devfor US,logfire-eu.pydantic.devfor EU) to help users identify their regionWhy
The remote MCP server is easier to set up and doesn't require users to manage a local process. Making it the first option in the README will help users get started faster.
🤖 Generated with Claude Code