Skip to main content
Glama
mshegolev

mshegolev/prometheus-mcp

by mshegolev

Related Servers

Alternatives to mshegolev/prometheus-mcp

No user-submitted related servers found.

    Related Servers

    • 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.
      115
      Apache 2.0
    • A
      license
      B
      quality
      C
      maintenance
      Enables interacting with Prometheus through MCP for querying metrics, series, alerts, rules, and server status using natural language.
      9
      102 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
      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
      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
      C
      maintenance
      MCP server that enables AI assistants to query and analyze Prometheus metrics through PromQL, with support for metric discovery and authentication.
      MIT

    TDQS

    A4.4/5.0

    Scored across 20 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose, with detailed descriptions including 'Don't use when' hints to prevent confusion. Overlapping tools like alertmanager_list_alerts and prometheus_list_alerts are well-differentiated by their focus on suppression state versus raw alert state.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern, prefixed by the subsystem (alertmanager_, prometheus_, correlate_, etc.). Verbs like get, list, query, and health_check are used predictably, making it easy for agents to infer tool function from name.

    Tool Count5/5

    20 tools cover a comprehensive monitoring domain including Prometheus and Alertmanager queries, status, alerts, targets, metadata, and advanced correlation. The number feels well-scoped without being overwhelming or too sparse.

    Completeness4/5

    The tool surface covers most read/analysis operations for Prometheus and Alertmanager, but lacks mutation capabilities like creating silences or updating configurations. For an investigation-focused MCP server, the coverage is strong, but minor gaps prevent a perfect score.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues