Mcp Observability Server

io.github.gagandeeppraPublished by GitHub account gagandeepprav0.1.3Updated Oct 24, 2026

MCP server for querying logs from observability platforms with unified search and tracing

VerifiedSTDIODesktop onlySecurity & Monitoring

Overview

AI-generated overview

A local MCP server that lets an assistant query logs from observability platforms through unified search and tracing, including New Relic.

What you can do
Query logs from observability platforms through a unified search interface, so an assistant can pull log data without switching tools. Follow traces across those platforms to investigate requests and incidents. Connect to New Relic using an account ID and API key supplied through environment variables.
When to use it
Useful when you want an assistant to look up logs or traces during debugging or incident investigation and you already work with an observability platform such as New Relic.
Requirements
Runs as a local process on the user's machine, installed from the PyPI package mcp-observability-server over stdio. Needs a Python environment and network access to the observability platform. New Relic integration requires the NEW_RELIC_ACCOUNT_ID and NEW_RELIC_API_KEY environment variables.
Before you install
Requires a New Relic API key in NEW_RELIC_API_KEY, which grants access to your observability account; keep it out of shared configuration. Queries send log and trace requests to the third-party observability platform. The manifest lists no tools, so the exact read or write behavior cannot be confirmed from the available information.

Installation

In SourceWeft

  1. Open Mcp Observability Server in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.3LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.