Skip to main content
Glama
carlyou

pagerduty-mcp-community

by carlyou
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PAGERDUTY_API_HOSTNoPagerDuty API host URL, defaults to https://api.pagerduty.com, use https://api.eu.pagerduty.com for EU accountshttps://api.pagerduty.com
PAGERDUTY_USER_API_KEYYesYour PagerDuty User API Token

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": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_alert_grouping_settingsB

List all alert grouping settings with optional filtering.

Args:
    query_model: Optional filtering parameters

Returns:
    List of alert grouping settings matching the query parameters
get_alert_grouping_settingB

Get details for a specific alert grouping setting.

Args:
    setting_id: The ID of the alert grouping setting to retrieve

Returns:
    Alert grouping setting details
list_incidentsA

List incidents with optional filtering.

Args:
    query_model: Optional filtering parameters

Returns:
    List of Incident objects matching the query parameters

Examples:
    Basic usage filtering by status:

    >>> from pagerduty_mcp.models import IncidentQuery
    >>> result = list_incidents(IncidentQuery(status=["triggered"]))
    >>> isinstance(result.response, list)
    True

    Multiple statuses with a limit:

    >>> result = list_incidents(IncidentQuery(status=["triggered", "acknowledged"], limit=10))
get_incidentA

Get a specific incident.

Args:
    incident_id: The ID or number of the incident to retrieve.

Returns:
    Incident details
list_servicesB

List all services.

Args:
    query_model: Optional filtering parameters

Returns:
    List of services matching the query parameters
get_serviceA

Get details for a specific service.

Args:
    service_id: The ID of the service to retrieve

Returns:
    The service details
list_teamsB

List teams based on the provided query model.

Args:
    query_model: The model containing the query parameters
Returns:
    List of teams.
get_teamA

Get a specific team.

Args:
    team_id: The ID or name of the team to retrieve
Returns:
    Team details
list_team_membersA

List members of a team.

Args:
    team_id: The ID of the team

Returns:
    List of UserReference objects
get_user_dataA

Get the current user's data.

Returns:
    User: User name, role, id, and summary and teams
list_usersA

List users, optionally filtering by name (query) and team IDs.

Args:
    query_model: Optional filtering parameters

Returns:
    List of users matching the criteria.
list_schedulesB

List schedules with optional filtering.

Returns:
    List of schedules matching the query parameters
get_scheduleA

Get a specific schedule by ID.

Args:
    schedule_id: The ID of the schedule to retrieve

Returns:
    Schedule details
list_schedule_usersA

List users in a schedule.

Args:
    schedule_id: The ID of the schedule

Returns:
    List of users in the schedule
list_oncallsB

List on-call schedules with optional filtering.

Returns:
    List of on-call schedules matching the query parameters
list_escalation_policiesB

List escalation policies with optional filtering.

Returns:
    List of escalation policies matching the query parameters
get_escalation_policyB

Get a specific escalation policy.

Args:
    policy_id: The ID of the escalation policy to retrieve

Returns:
    Escalation policy details
list_event_orchestrationsB

List event orchestrations with optional filtering.

Args:
    query_model: Optional filtering parameters

Returns:
    List of event orchestrations matching the query parameters
get_event_orchestrationA

Get details for a specific event orchestration.

Args:
    orchestration_id: The ID of the event orchestration to retrieve

Returns:
    The event orchestration details
get_event_orchestration_routerA

Get the router configuration for a specific event orchestration.

Args:
    orchestration_id: The ID of the event orchestration to retrieve router for

Returns:
    The event orchestration router configuration

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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 20 tools

Disambiguation5/5

Each tool targets a distinct resource or specific sub-resource (e.g., get_escalation_policy vs list_escalation_policies, get_event_orchestration_router). No two tools have overlapping purposes, making selection unambiguous.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern using snake_case: get_<resource> for single items, list_<resource> for collections. There are no deviations or mixed conventions.

Tool Count5/5

With 20 tools covering the major PagerDuty resources (incidents, services, teams, users, schedules, escalation policies, etc.), the count is appropriate for a comprehensive read-only API surface.

Completeness2/5

The server is entirely read-only; there are no create, update, delete, or action tools (e.g., acknowledge incident, create service). This is a significant gap for most workflows, leaving agents unable to take any action.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources