Skip to main content
Glama
idanfishman

prometheus-mcp

by idanfishman

Related Servers

Alternatives to prometheus-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      F
      maintenance
      A Model Context Protocol server that enables AI assistants to query Prometheus metrics, discover available data, and analyze system performance through natural language interactions.
      5
      62 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that enables AI assistants to query and analyze Prometheus metrics through PromQL, with support for metric discovery and authentication.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI agents to interact directly with Prometheus metrics data through natural language queries.
      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
      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.
      109
      Apache 2.0
    • 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

    TDQS

    B3.4/5.0

    Scored across 10 tools

    Disambiguation4/5

    Most tools target distinct Prometheus resources, and the descriptions make the boundaries clear. The main ambiguities are list_targets vs scrape_pool_targets and list_labels vs label_values, which are related but scope-differentiated.

    Naming Consistency3/5

    All tool names share the prometheus_ prefix and snake_case, but the pattern is mixed: some use list_* verbs, others use bare nouns like runtime_info or query_range. This is readable but not a consistent verb_noun convention.

    Tool Count5/5

    Ten tools is well-scoped for a Prometheus MCP server, covering querying, metadata, targets, and informational endpoints without unnecessary bloat.

    Completeness4/5

    The surface covers core query, range query, metric metadata, label values, and target discovery. Missing alerting/rules or series endpoints, but the main monitoring workflows are well supported.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues