Skip to main content
Glama
Prometheus Safe MCP

Prometheus Safe MCP

by bgauger

Related Servers

Alternatives to Prometheus Safe MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      Enables agents to query and explore Prometheus through PromQL, metric and label discovery, alerts, rules, scrape health, and cardinality, while keeping admin writes disabled unless explicitly enabled.
      12
      519 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to execute PromQL queries and discover metrics across multiple Prometheus tenants using the Model Context Protocol. It supports single and multi-tenant configurations with secure authentication for instant and range query analysis.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to query Prometheus metrics, monitor alerts, and analyze system health through read-only access to your Prometheus server with built-in query safety and optional AI-powered metric analysis.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP-compatible agents to run governed, read-only analytics queries against Postgres using predefined metrics and dimensions, with safety checks and provenance on every result.
      39 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables an MCP client to answer business questions by running read-only, allow-listed, masked SQL queries against a served database copy, with row/time limits and an audit log.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables read-only querying and exploration of Grafana Loki logs and LogQL metrics, including labels, fields, volume, stats, patterns, rules, and contextual log retrieval, with responses shaped for context windows.
      14
      552 npm
      MIT

    TDQS

    C2/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool targets a clearly distinct aspect of Prometheus: querying metrics, listing active alerts, and checking target health. There is no functional overlap between them, making tool selection unambiguous.

    Naming Consistency5/5

    All three tool names follow a consistent snake_case convention with a noun-like pattern (prometheus_query, active_alerts, target_health). The names are predictable and reflect their purpose without mixing conventions.

    Tool Count4/5

    Three tools is a lean but reasonable count for a minimal Prometheus integration, covering the most common read-only operations. It feels slightly thin for a full-featured server but is appropriate for a focused purpose.

    Completeness3/5

    The surface covers core operations (query, alerts, health) but lacks obvious complementary features like range queries, alert rule management, or metric metadata retrieval. Agents may need to work around these gaps for more complex workflows.

    Maintenance

    ActivityStale
    ResponsivenessOutdated data