Skip to main content
Glama
JoaoAndrade18

MCP Observability Server

by JoaoAndrade18
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to MCP Observability Server

No user-submitted related servers found.

    Related Servers

    • devops-mcp-server

      rpsangam
      F
      license
      Not graded
      quality
      C
      maintenance
      Exposes DevOps/SRE operations like Kubernetes pod status, Prometheus metrics queries, and deploy history as tools for MCP-compatible clients.
      -

    • Nibble

      Talia04
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to investigate production incidents by exposing service health, logs, and deployment data through MCP tools.
      10 npm
      -

    • MCP Observability Server

      Sushma243
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server for observability that provides tools for log search, metrics inspection, SQL querying, incident summaries, and service discovery.
      -

    • mcp-incident-copilot

      ShreyAC962
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that provides guarded, audited, read-only access to ops tooling (alerts, metrics, logs, deploys, runbooks) and a triage agent that diagnoses incidents end-to-end with CI-verified root cause analysis.
      MIT

    • opsagent

      batpepe
      A
      license
      Not graded
      quality
      B
      maintenance
      A read-only MCP server that exposes Kubernetes cluster telemetry tools (pods, events, logs, metrics, ArgoCD syncs) with automatic redaction for incident triage and hypothesis ranking.
      MIT

    • CloudOps MCP

      bienherasme
      A
      license
      A
      quality
      B
      maintenance
      CloudOps MCP is a read-only Model Context Protocol server that exposes normalized operational infrastructure context (logs, metrics, deployments, health) to AI agents through a small set of typed, bounded tools.
      6
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.4/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: service discovery, log search, metric retrieval, deploy history, deploy-error correlation, and incident creation. There is no overlap between these functions, and the correlator tool explicitly bundles several lower-level operations, reducing potential confusion.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in lowercase snake_case (list_services, query_logs, get_metrics, get_deploys, correlate_deploy_with_errors, open_incident). The verbs are specific to each action, and the naming style is uniform across the set.

    Tool Count5/5

    Six tools is well within the ideal range for a focused observability server. Each tool earns its place by covering a distinct aspect of monitoring and operations, without unnecessary bloat or missing essential capabilities.

    Completeness4/5

    The set covers the core observability workflow: discovering services, inspecting logs, fetching metrics with SLO status, reviewing deploys, and opening incidents. A minor gap is the lack of incident management features beyond creation (e.g., listing or updating incidents), but this is secondary to the server's primary monitoring purpose.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources