Skip to main content
Glama
PagerDuty

pagerduty-mcp

Official
by PagerDuty
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to pagerduty-mcp

No user-submitted related servers found.

    Related Servers

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

      carlyou
      A
      license
      A
      quality
      C
      maintenance
      A community-maintained MCP server for interacting with PagerDuty accounts, enabling management of incidents, services, schedules, and event orchestrations through MCP-enabled clients.
      20
      1
      Apache 2.0
    • runframe-mcp-server by runframe

      runframe-mcp-serverofficial

      runframe
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables managing incident response workflows including incidents, on-call, postmortems, and more through the Runframe platform using MCP tools.
      40 npm
      4
      MIT

    • mcp-allquiet

      iagogfe
      A
      license
      A
      quality
      B
      maintenance
      Enables incident management and on-call operations for the All Quiet platform, allowing MCP clients to triage incidents, check who is on call, and access the full public API through generic tools.
      10
      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.4/5.0

    Scored across 63 tools

    Disambiguation5/5

    Every tool targets a distinct entity or specific sub-aspect of an entity (e.g., get_incident vs. get_outlier_incident, list_schedule_v3_rotations vs. list_schedule_v3_rotation_events). No two tools have overlapping purposes.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern using 'get_' for single resources and 'list_' for collections. There is no mixing of camelCase or other conventions.

    Tool Count2/5

    63 tools is far above the typical well-scoped range (3-15). While the tool count covers many PagerDuty entities, the sheer number makes the surface difficult to navigate and suggests insufficient consolidation.

    Completeness1/5

    The server is entirely read-only with no create, update, delete, or action tools (e.g., acknowledge_incident, create_service). For an incident management platform, this is a severe gap that prevents agents from performing any operational actions.

    Maintenance

    ActivitySlowing
    ResponsivenessUnresponsive

    Resources