Skip to main content
Glama
WYRE-AI

AlertOps MCP Server

by WYRE-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to AlertOps MCP Server

No user-submitted related servers found.

    Related Servers

    • Sprinklr MCP Server

      daiict218
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants read-only access to Sprinklr data via MCP, allowing querying reports, searching cases, and calling Sprinklr API endpoints.
      4 npm
      ISC

    • chatwoot-mcp

      minholi
      A
      license
      B
      quality
      C
      maintenance
      Provides AI assistants with read-only access to Chatwoot analytics and operational data, including conversations, agents, inboxes, teams, CSAT, and real-time metrics.
      30
      1
      MIT

    • Cisco Duo MCP Server

      WYRE-AI
      F
      license
      A
      quality
      B
      maintenance
      Provides AI assistants with read-only access to Cisco Duo identity and MFA administration data, including users, enrolled devices, tokens, groups, integrations, and authentication/administrator/telephony logs.
      22
      -
    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/5.0

    Scored across 11 tools

    Disambiguation5/5

    Every tool targets a distinct resource/action: alerts, inbound-ID lookups, users, contact methods, groups, topics, integrations, on-call, and schedules. The two inbound-ID resolution tools are similar but clearly separated by identifier type (messageID vs uniqueInboundID) and well-described.

    Naming Consistency5/5

    All tools follow the same alertops_ prefix with a consistent list/get verb pattern (e.g., alertops_list_alerts, alertops_get_user_schedule). The naming is uniform and predictable across the entire set.

    Tool Count5/5

    11 tools is well-scoped for an AlertOps read/query-focused server. Each tool covers a meaningful data surface without redundancy, and the count stays in the ideal range.

    Completeness3/5

    The read/query surface is solid: alerts, users, groups, topics, integrations, and schedules are all represented. However, there are no alert lifecycle actions (acknowledge, resolve, assign) or any mutating operations, which is a notable gap for operational incident management workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources