Skip to main content
Glama
mshegolev/prometheus-mcp

mshegolev/prometheus-mcp

Related Servers

Alternatives to mshegolev/prometheus-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that lets LLMs interact with a running Prometheus instance via its API, enabling metric analysis, PromQL queries, and rule/target inspection. It also provides embedded documentation and guided runbooks for common Prometheus tasks.
      142
      Apache 2.0
    • A
      license
      B
      quality
      D
      maintenance
      Enables interacting with Prometheus through MCP for querying metrics, series, alerts, rules, and server status using natural language.
      9
      224 npm
      6
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A lean MCP server that provides LLM agents with transparent access to multiple Prometheus instances for metrics analysis and SRE operations.
      4
      GPL 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Gives AI clients read-only access to Prometheus, letting them discover metrics, run instant and range PromQL queries, and inspect scrape targets and firing alerts. Results are capped and downsampled with per-series min/max/avg/last summaries so answers stay token-efficient.
      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

    TDQS

    A4.1/5.0

    Scored across 21 tools

    Disambiguation4/5

    Most tools map cleanly to a distinct API endpoint, and descriptions explicitly cross-reference siblings (prometheus_list_alerts vs alertmanager_list_alerts, query vs query_range). The main ambiguity is among the three alert analytics tools (correlate_alerts_across_instances, group_alerts_by_service, detect_cascading_alerts), which all describe related-cluster/cascade analysis over the same alert data and rely on prose rather than distinct inputs to steer selection.

    Naming Consistency4/5

    The dominant pattern is subsystem-prefixed snake_case verb_noun (prometheus_query, prometheus_list_targets, alertmanager_list_silences, federation_list_instances), which is very predictable. Deviations are the three unprefixed verb-first analytics tools (correlate_alerts_across_instances, group_alerts_by_service, detect_cascading_alerts), which break the prefix convention but remain readable.

    Tool Count3/5

    21 tools is on the heavy side for a read-only monitoring proxy, though it spans three real domains (Prometheus API, Alertmanager API, federation/health). Several introspection tools (build_info, runtime_info, cardinality, health_check, metadata) are each thin wrappers around a single endpoint and could plausibly be consolidated.

    Completeness4/5

    Coverage is strong for read/diagnostic workflows: instant and range queries, metadata, label, metric and target discovery, rules, alerts, TSDB cardinality, runtime/build info, health, plus Alertmanager status, alerts, silences, and groups. Gaps are mostly write/lifecycle operations (creating or expiring silences, modifying rules) that an investigation-focused agent could want during incident mitigation.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues