Skip to main content
Glama
weetime

prometheus-mcp-server

by weetime

Related Servers

Alternatives to prometheus-mcp-server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides access to Prometheus metrics and queries, allowing AI assistants to execute PromQL queries and analyze metrics data through standardized MCP interfaces.
      MIT
    • A
      license
      Not graded
      quality
      A
      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.
      117
      Apache 2.0
    • A
      license
      A
      quality
      B
      maintenance
      MCP server for Prometheus metrics and observability. Give Claude (or any MCP-capable agent) read access to your Prometheus instance — query metrics with PromQL, inspect active alerts, and explore scrape targets without leaving the conversation. Tools: prometheus_list_metrics, prometheus_query, prometheus_query_range, prometheus_list_alerts, prometheus_list_targets.
      20
      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
      B
      quality
      D
      maintenance
      Provides seamless integration between AI assistants and Prometheus, enabling natural language interactions with your monitoring infrastructure. This server allows for effortless querying, discovery, and analysis of metrics.
      10
      1,220 npm
      27
      MIT

    TDQS

    B3.2/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool has a distinct, clearly defined purpose. The instant-query and range-query are differentiated by query type, while the other tools retrieve specific Prometheus resources (series, labels, metadata, targets, alerts, rules, status) without overlap.

    Naming Consistency4/5

    Most tool names follow a verb_noun pattern (get-series, get-label-values, get-metadata, etc.), but the query tools break the pattern with 'instant-query' and 'range-query' where 'query' comes after the adjective. This is a minor deviation but still readable and predictable.

    Tool Count5/5

    Nine tools is well-scoped for a Prometheus server, covering the core read operations without redundancy. Each tool earns its place by providing a unique capability.

    Completeness4/5

    The surface covers the main read operations (query, series, labels, metadata, targets, alerts, rules, status), which is appropriate for a read-only Prometheus server. However, it lacks write operations (e.g., creating or modifying rules/alerts) and advanced query features (e.g., query for multiple time points or metric discovery).

    Maintenance

    ActivityInactive
    ResponsivenessNo issues