Skip to main content
Glama
carlyou

pagerduty-mcp-community

by carlyou

Related Servers

Alternatives to pagerduty-mcp-community

No user-submitted related servers found.

    Related Servers

    • 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
    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for IncidentRelay, exposing its entire REST API (279 operations) through gateway and curated tools for on-call scheduling, alert routing, and incident management.
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      A modular MCP server exposing tools for integrating with services like GitHub, Redash, Jenkins, Figma, Jira, Confluence, Teams, Datadog, PagerDuty, Slack, and Presto, enabling users to manage these platforms through natural language via an MCP client.
      -
    • A
      license
      B
      quality
      C
      maintenance
      Unified MCP server for DevOps engineers that provides real-time read and write access to Kubernetes, ArgoCD, Prometheus, and PagerDuty from any MCP-compatible AI agent.
      21
      73 npm
      3
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      An incident management MCP server for on-call engineers, providing tools to search incidents, review deploys, query logs, analyze latency metrics, and acknowledge or summarize incidents.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for the Splunk On-Call (VictorOps) API providing comprehensive incident management, on-call schedules, team administration, and alert reporting through natural language.
      MIT

    TDQS

    A3.7/5.0

    Scored across 20 tools

    Disambiguation5/5

    Each tool targets a distinct resource or specific sub-resource (e.g., get_escalation_policy vs list_escalation_policies, get_event_orchestration_router). No two tools have overlapping purposes, making selection unambiguous.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern using snake_case: get_<resource> for single items, list_<resource> for collections. There are no deviations or mixed conventions.

    Tool Count5/5

    With 20 tools covering the major PagerDuty resources (incidents, services, teams, users, schedules, escalation policies, etc.), the count is appropriate for a comprehensive read-only API surface.

    Completeness2/5

    The server is entirely read-only; there are no create, update, delete, or action tools (e.g., acknowledge incident, create service). This is a significant gap for most workflows, leaving agents unable to take any action.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues