PagerDuty's official MCP server provides tools to interact with your PagerDuty account through MCP-enabled clients. It supports managing incidents, services, schedules, event orchestrations, and more directly from the client. Prerequisites include asdf-vm, uv, and a PagerDuty User API Token. The README describes configuring the server in MCP clients such as Cursor and Visual Studio Code, using environment variables like PAGERDUTY_USER_API_KEY and PAGERDUTY_API_HOST (EU users can point to the EU API host). By default, the MCP server exposes read-only tools; to enable write operations you must launch with the --enable-write-tools flag. The documentation also covers local setup (cloning, installing asdf plugins, installing uv, syncing dependencies) and running the server via uv or uvx with the appropriate arguments. It provides integration examples for Cursor, VS Code, and Claude Desktop, including sample JSON configuration snippets. The available toolset spans across Incidents, Event Orchestrations, Escalation Policies, Teams, Users, On-call, Schedules, Services, and Status Pages, as well as alert grouping settings; many tools are read-only by default and require write-tools to modify PagerDuty data.