Skip to main content
Glama
elizabethpammi

prom-evidence-mcp

by elizabethpammi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to prom-evidence-mcp

No user-submitted related servers found.

    Related Servers

    • Prometheus MCP Server

      bartest5
      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

    • Proms MCP Server

      app-sre
      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
    • prometheus-mcp-server by prometheus

      prometheus-mcp-serverofficial

      prometheus
      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.
      106
      Apache 2.0

    • prometheus-mcp-server

      ramkrsna
      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

    • Prometheus MCP Server

      yanmxa
      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
      92 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct operation: instant queries, range queries, metric listing, and target health. There is no overlap in purpose, and the descriptions reinforce when each should be used.

    Naming Consistency4/5

    Names are lowercase snake_case and readable, with instant_query and range_query following a clear pattern. list_metrics and target_health deviate slightly from the adjective_noun style but remain predictable and unambiguous.

    Tool Count5/5

    Four tools is well-scoped for a focused Prometheus evidence server, covering the essential query and health-check operations without unnecessary bloat.

    Completeness4/5

    The core workflow of verifying target health, confirming metric existence, and running instant/range queries is covered. Minor gaps exist such as label value enumeration or metric metadata, but agents can work around these with the available tools.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources