Observability. MCP servers, the command line and skills for connecting an agent to PagerDuty.
Published by PagerDuty's owner: we named it as the system's official server after reading its registry record, or it is published under PagerDuty's own domain. See what first-party means.
PagerDuty's official MCP server which provides tools to interact with your PagerDuty account.
pagerduty-mcp version 0.2.1, runs over stdioVersion 0.2.1. Registry record last changed .
2 servers for PagerDuty that name a public repository or a package. Anyone can publish one, and we have not read their code: check the publisher and the source before giving one a credential.
In this order: live servers before deprecated ones, first-party first, a known vulnerability last, then more downloads, then a more recent push, then by name. There is no score. Downloads are from npm and pypistats, the last push from GitHub and vulnerabilities from OSV; a server's own page has the day each was read, and "not read" means we have no figure, not that there is none. See how this directory is made.
| Server | Publisher | Reach | Downloads a week | Last push | Vulnerabilities |
|---|---|---|---|---|---|
| com.mcparmory/pagerduty | Sourced | PyPIContainer image | 150 | not read | none known |
PagerDuty MCPio.github.Servosity/pagerduty-mcp | Sourced | MCP bundle | not read | not read | not checked |
A server is listed for PagerDuty when we have named it as the system's official server, when its registry title or the last part of its registry name names PagerDuty as whole words, or when it is published under PagerDuty's own domain. See how this directory is made.
Built from agent catalog version 2026-11-13.3 of , from the MCP Registry as read on . A listing here is not an endorsement: anyone can publish a server, and we have not read its code. Names, descriptions and addresses are the publisher's own. See how this directory is made, and tell us about a wrong entry through the contact page.