Skip to main content
Glama
Sign In
PagerDuty MCP Server

PagerDuty MCP Server

by wpfleger96
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to PagerDuty MCP Server

No user-submitted related servers found.

    Related Servers

    • OpenAPI MCP Server

      ivo-toby
      A
      license
      Not graded
      quality
      C
      maintenance
      A server that enables Large Language Models to discover and interact with REST APIs defined by OpenAPI specifications through the Model Context Protocol.
      11,739 npm
      301
      MIT

    • OpenAPI MCP Server

      rahgadda
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol Server that enables LLMs to interact with and execute REST API calls through natural language prompts, supporting GET/PUT/POST/PATCH operations on configured APIs.
      6
      Apache 2.0

    • Swagger/Postman MCP Server

      AlanGreyjoy
      A
      license
      Not graded
      quality
      D
      maintenance
      Server that ingests Swagger/OpenAPI specifications and Postman collections, providing just 4 strategic tools that allow AI agents to dynamically discover and interact with APIs instead of generating hundreds of individual tools.
      3
      ISC

    • MCP Salesforce Connector

      ampcome-mcps
      A
      license
      B
      quality
      D
      maintenance
      A server implementation that enables LLMs to interact with Salesforce data through SOQL queries, SOSL searches, and API operations including retrieving, creating, updating, and deleting records.
      10
      1
      MIT
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    A3.5/5.0

    Scored across 12 tools

    Disambiguation4/5

    Most tools target distinct resources or incident actions, and the read tools are clearly resource-specific. The main potential overlap is between get_oncalls and list_users_oncall, which both concern on-call data but differ in whether they return entries or users; descriptions help but still leave minor ambiguity.

    Naming Consistency4/5

    Almost all tools use consistent snake_case action-plus-object naming. The main deviation is list_users_oncall versus the get_* pattern used for other read/list operations, plus build_user_context as a special utility, but overall the convention is predictable.

    Tool Count5/5

    Twelve tools is a well-scoped size for a PagerDuty integration, covering reads across key resources plus incident response actions. Each tool has a clear place and the set does not feel bloated or thin.

    Completeness3/5

    The core incident response workflow is represented with get_incidents, acknowledge_incident, add_incident_note, and resolve_incident, alongside reads for users, teams, services, policies, schedules, and oncalls. However, notable lifecycle operations are missing, such as creating/triggering incidents, updating or reassigning incidents, retrieving incident notes, and schedule overrides.

    Maintenance

    ActivityMaintained
    ResponsivenessLimited data

    Resources