Skip to main content
Glama
wpfleger96

PagerDuty MCP Server

by wpfleger96
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PAGERDUTY_API_TOKENNoYour PagerDuty API token for authentication.
PAGERDUTY_CLIENT_IDNoClient ID for OAuth 2.0 PKCE authentication (required if not using API token).
PAGERDUTY_CLIENT_SECRETNoOptional client secret for OAuth token refresh (confidential client).
PAGERDUTY_OAUTH_CALLBACK_PORTNoPort for OAuth callback (default: 5173).5173

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
extensions
{
  "io.modelcontextprotocol/ui": {}
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_escalation_policiesA

Get PagerDuty escalation policies by filters or get details for a specific policy ID.

get_incidentsB

Get PagerDuty incidents by filters or get details for a specific incident ID or number.

acknowledge_incidentB

Acknowledge a PagerDuty incident. This signals that someone is actively working on the incident.

resolve_incidentA

Resolve a PagerDuty incident. This marks the incident as resolved and stops any further escalations.

add_incident_noteA

Add a note to a PagerDuty incident. Notes are used to record additional context, investigation progress, or resolution details.

get_oncallsA

List on-call entries for schedules, policies, or time ranges.

Behavior varies by time parameters:

  1. Without since/until: Returns current on-calls Example: get_oncalls(schedule_ids=["SCHEDULE_123"])

  2. With since/until: Returns all on-calls in range Example: get_oncalls(schedule_ids=["SCHEDULE_123"], since="2024-03-20T00:00:00Z", until="2024-03-27T00:00:00Z")

get_schedulesB

Get PagerDuty schedules by filters or get details for a specific schedule ID.

list_users_oncallC

List the users on call for a schedule during the specified time range.

get_servicesA

Get PagerDuty services by filters or get details for a specific service ID.

get_teamsA

Get PagerDuty teams by filters or get details for a specific team ID.

get_usersB

Get PagerDuty users by filters or get details for a specific user ID.

build_user_contextA

Validate and build the current user's context into a dictionary with the following format: { "user_id": str, "team_ids": List[str], "service_ids": List[str], "escalation_policy_ids": List[str] } The MCP server tools use this user context to filter the following resources: - Escalation policies - Incidents - Oncalls - Services - Users

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
get_tool_documentation

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/wpfleger96/pagerduty-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server