Skip to main content
Glama
yanmxa

Prometheus MCP Server

by yanmxa

Related Servers

Alternatives to Prometheus MCP Server

No user-submitted related servers found.

    Related Servers

    • 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
    • A
      license
      Not graded
      quality
      D
      maintenance
      A tool that enables access to Prometheus metrics data through a Model Context Protocol server, allowing interaction with monitoring data using natural language.
      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
      346 npm
      27
      MIT
    • A
      license
      Not graded
      quality
      F
      maintenance
      An MCP server that enables Large Language Models to retrieve, analyze, and query metric data from Prometheus databases through pre-defined routes.
      33
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Provides access to Prometheus metrics and queries through standardized Model Context Protocol interfaces, allowing AI assistants to execute PromQL queries and analyze metrics data.
      6
      518
      MIT

    TDQS

    B3.1/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: discovery, metadata retrieval, instant queries, range queries, and target monitoring. There is no overlap in functionality, making it easy for an agent to select the right tool for each task without confusion.

    Naming Consistency5/5

    All tools follow a consistent 'prom_' prefix with descriptive suffixes (discover, metadata, query, range, targets). This uniform naming pattern enhances readability and predictability across the tool set.

    Tool Count5/5

    With 5 tools, this server is well-scoped for Prometheus monitoring tasks. Each tool serves a specific, essential function in the domain, and the count is neither too sparse nor overwhelming for the intended purpose.

    Completeness4/5

    The tool set covers core Prometheus operations well, including querying, metadata, and target discovery. A minor gap exists in lacking explicit alert or rule management tools, but agents can still perform most monitoring workflows effectively with the provided tools.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive