PagerDuty MCP server

by PagerDuty

Incidents, services, schedules and who is on call.

What it can do

  • Manage incidents
  • Check on-call
  • List services
  • Add incident notes

Through MCP1, every tool call is checked against your groups and rules, and recorded in the audit log.

How it connects

Connects with a token (User API token). Enter it as Token token=<your key>. Create it in My profile, User settings. MCP1 encrypts it at rest.

Endpoint
https://mcp.pagerduty.com/mcp
Regions
US, EU
Transport
Streamable HTTP

With MCP1

PagerDuty for the whole team, behind one URL

  1. 01

    Install it once

    An admin adds PagerDuty from the MCP1 catalog. Its authentication or token stays sealed in MCP1, never on a laptop.

  2. 02

    Decide who gets what

    Open it to groups, fully or read-only, and set rules per tool. Destructive tools can need an admin.

  3. 03

    Connect any client

    Claude, Cursor, ChatGPT, Codex and the rest connect one gateway URL and sign in with their own account.

More for engineering

See all engineering servers
  • GitHubEngineering

    Repositories, issues, pull requests, code search and Actions.

    Token
  • GitLabEngineering

    Projects, issues, merge requests and pipelines on GitLab.com.

    One-click auth
  • Projects, issues, merge requests and pipelines on your own GitLab.

    One-click auth
  • LinearEngineering

    Find, create and update issues, projects and comments.

    One-click auth
  • SentryEngineering

    Search errors, triage issues and analyze performance.

    One-click auth
  • VercelEngineering

    Projects, deployments, runtime logs and the Vercel docs.

    One-click auth