Skip to main content
Glama
angelus-h

PagerDuty MCP Server

by angelus-h
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to PagerDuty MCP Server

No user-submitted related servers found.

    Related Servers

    • PagerDuty MCP Server

      dinesh-it
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to interact with PagerDuty services, incidents, schedules, and on-call management through natural language.
      -

    • pagerduty-mcp

      chenzhaoxuan0
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables PagerDuty incident response operations including listing incidents, acknowledging and resolving incidents, looking up on-call schedules, and listing services.
      MIT
    • pagerduty-mcp by PagerDuty

      pagerduty-mcpofficial

      PagerDuty
      A
      license
      B
      quality
      F
      maintenance
      Enables management of PagerDuty incidents, services, schedules, and more directly from MCP-enabled clients, with embedded interactive UIs for incident command center, on-call management, and other features.
      63
      77
      Apache 2.0

    • Opsgenie MCP Server

      burakdirin
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables comprehensive Opsgenie alert management including listing, creating, acknowledging, and closing alerts, as well as managing alert notes, logs, and custom properties through natural language.
      168
      MIT

    • DataDog MCP Server

      Believe-SA
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with DataDog's observability platform through a standardized interface. Supports monitoring infrastructure, managing events, analyzing logs and metrics, and automating operations like alerts and downtimes.
      1
      MIT
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    A3.8/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: specific incident retrieval, user-specific incident listing, general listing, and incident lifecycle actions (acknowledge, resolve, note) are clearly separated. Specialized views like alerts and timeline also have unique purposes with no overlap.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (e.g., get_incident, resolve_incident, list_incidents). The only slight deviation is get_my_incidents and get_oncall, but they still fit the verb_noun convention clearly.

    Tool Count5/5

    With 9 tools, the server is well-scoped for incident management and on-call visibility. Each tool serves a distinct purpose without redundancy or unnecessary bloat.

    Completeness4/5

    The server covers the core incident lifecycle: list, view, acknowledge, resolve, add notes, plus related context (alerts, timeline, on-call). However, it lacks the ability to create or reassign incidents, which are common operational actions, representing a minor gap.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources