Skip to main content
Glama
Sign In
PagerDuty MCP Server

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
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to interact with PagerDuty services, incidents, schedules, and on-call management through natural language.
      MIT

    • 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

    • AlertOps MCP Server

      WYRE-AI
      A
      license
      A
      quality
      B
      maintenance
      Enables read-only access to AlertOps incident alerting and on-call data, including alerts, users, groups, integrations, and schedules, for AI assistants.
      11
      Apache 2.0

    • Rootly MCP Server

      MSPbotsAIFramework
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to read incidents, alerts, on-call schedules, teams, severities and API user info, and — on explicit request — declare, update and resolve incidents, manage alerts, and create or update teams through the Rootly REST API. It is stateless and multi-tenant, taking the API token as a per-request HTTP header that is never stored.
      Apache 2.0

    • fettle-mcp

      fettlesh
      A
      license
      A
      quality
      B
      maintenance
      Uptime monitoring your AI agent can set up: create HTTP, SSL, ping, TCP and DNS monitors checked from multiple regions, run checks on demand, read and acknowledge incidents, manage cron heartbeats, maintenance windows and status page updates.
      56
      816 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

    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 recent community issues

    Resources