Skip to main content
Glama
wpfleger96

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
      B
      maintenance
      A server that enables Large Language Models to discover and interact with REST APIs defined by OpenAPI specifications through the Model Context Protocol.
      3,228 npm
      294
      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.
      318 PyPI
      6
      Apache 2.0

    • Swagger/Postman MCP Server

      AlanGreyjoy
      F
      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
      -

    • 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
    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.7/5.0

    Scored across 12 tools

    Disambiguation4/5

    Most tools target distinct resources with clear actions. Slight overlap between get_oncalls and list_users_oncall, but descriptions clarify different use cases. Overall well-disambiguated.

    Naming Consistency5/5

    All tools use consistent snake_case with a verb_noun pattern (e.g., acknowledge_incident, get_services). No mixing of styles, making it predictable for an agent.

    Tool Count5/5

    12 tools covering incident actions, resource retrieval, and user context building is well-scoped for a PagerDuty incident response server. Neither too sparse nor unnecessarily large.

    Completeness4/5

    Incident lifecycle includes acknowledge, note, get, resolve, but missing create_incident or update_incident. Resource operations are read-only. For incident response context, surface is reasonably complete.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources