Skip to main content
Glama
ntk148v

alertmanager-mcp-server

by ntk148v
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to alertmanager-mcp-server

No user-submitted related servers found.

    Related Servers

    • 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

    • 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 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

    • observability-mcp

      ThainaJardim
      A
      license
      A
      quality
      D
      maintenance
      MCP server that enables AI assistants to query Grafana/Loki logs and Thanos/Prometheus metrics directly from MCP-compatible clients like Cursor or Claude Desktop.
      8
      MIT

    • 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
    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

    B3.1/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action (e.g., get vs post, alerts vs silences vs status). There is no overlap; get_alert_groups and get_alerts are clearly differentiated.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with lowercase underscores: delete_, get_, post_. No mixing of styles or irregular verbs.

    Tool Count5/5

    With 9 tools covering common Alertmanager operations (list, get, create, delete for alerts and silences, plus status and receivers), the count is well-scoped for the domain.

    Completeness4/5

    Covers core alert and silence lifecycle management, status, and receivers. A minor gap: no tool to update alert fields or manage alert rules, but these are outside Alertmanager's typical CRUD.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources