Source profileQuality 96/100

WYRE-AI/msp-claude-plugins/msp-claude-plugins/pagerduty/pagerduty/skills/api-patterns/SKILL.md

PagerDuty API Patterns

PagerDuty API and hosted MCP fundamentals: US/EU MCP endpoints, the `Token token=` auth header and token types, the complete 66-tool reference across 13 categories (incidents, on-call, schedules, escalation policies, services, event orchestrations, status pages, teams, users, and more), offset pagination, common filter parameters, rate limits, and error codes.

Source repository stars
42
Declared platforms
0
Static risk flags
0
Last source update
2026-08-28
Source checked
2026-08-28
DecisionCompatibilityInstallWorkflowPermissionsEvidenceSourceFAQ

Decision brief

What it does: where it fits

PagerDuty API and hosted MCP fundamentals: US/EU MCP endpoints, the `Token token=` auth header and token types, the complete 66-tool reference across 13 categories (incidents, on-call, schedules, escalation policies, services, event orchestrations, status pages, teams, users, and more), offset pagination, common filter parameters, rate limits, and error cod…

Best for

    Not for

    • Tasks that require unconfirmed production actions or broad system permissions.
    • Environments where the pinned source and install steps cannot be inspected.

    Compatibility matrix

    Platform support, with evidence labels

    PlatformStatusEvidenceWhat to check
    CodexNot declaredNo explicit evidencePortability before use
    Claude CodeNot declaredNo explicit evidencePortability before use
    CursorNot declaredNo explicit evidencePortability before use
    Gemini CLINot declaredNo explicit evidencePortability before use
    Open the compatibility checker

    Installation

    Inspect first. Install second.

    The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

    Source-detected install commandSource
    npx skills add https://github.com/WYRE-AI/msp-claude-plugins --skill "msp-claude-plugins/pagerduty/pagerduty/skills/api-patterns"
    Safe inspection promptEditorial

    Inspect the Agent Skill "PagerDuty API Patterns" from https://github.com/WYRE-AI/msp-claude-plugins/blob/5005f73ba2f52cd299f58aa6bb79f4e70ae87103/msp-claude-plugins/pagerduty/pagerduty/skills/api-patterns/SKILL.md at commit 5005f73ba2f52cd299f58aa6bb79f4e70ae87103. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

    Workflow

    What the source asks the agent to do

    1. 01

      Authentication

      User API tokens are preferred — they carry individual audit attribution and work for all 66 MCP tools.

      User API tokens are preferred — they carry individual audit attribution and work for all 66 MCP tools.For EU PagerDuty accounts, the gateway operator sets VENDORURLPAGERDUTY=https://mcp.eu.pagerduty.com. No change needed in your API token.The MCP Gateway stores your token as an org credential and automatically forwards:
    2. 02

      Token Type and Header Format

      User API tokens are preferred — they carry individual audit attribution and work for all 66 MCP tools.

      User API tokens are preferred — they carry individual audit attribution and work for all 66 MCP tools.
    3. 03

      EU Region

      For EU PagerDuty accounts, the gateway operator sets VENDORURLPAGERDUTY=https://mcp.eu.pagerduty.com. No change needed in your API token.

      For EU PagerDuty accounts, the gateway operator sets VENDORURLPAGERDUTY=https://mcp.eu.pagerduty.com. No change needed in your API token.
    4. 04

      How the Gateway Injects Credentials

      The MCP Gateway stores your token as an org credential and automatically forwards:

      The MCP Gateway stores your token as an org credential and automatically forwards:
    5. 05

      Complete MCP Tool Reference (66 Tools)

      Review the “Complete MCP Tool Reference (66 Tools)” section in the pinned source before continuing.

      Review and apply the “Complete MCP Tool Reference (66 Tools)” source section.

    Permission review

    Static risk signals and limitations

    No configured static risk pattern was detected

    This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.

    Evidence record

    Why each signal appears

    EvidenceSourceComputedTestedEditorial
    SignalValueEvidence typeMeaning
    Quality score96/100ComputedDocumentation, specificity, maintenance, and trust rules
    Repository stars42SourceRepository attention, not individual Skill quality
    Compatibility0 platformsSourceDeclared in the catalog source record
    Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

    Pinned source

    Provenance and original SKILL.md

    Repository
    WYRE-AI/msp-claude-plugins
    Skill path
    msp-claude-plugins/pagerduty/pagerduty/skills/api-patterns/SKILL.md
    Commit
    5005f73ba2f52cd299f58aa6bb79f4e70ae87103
    License
    Apache-2.0
    Collected
    2026-08-28
    Default branch
    main
    View the original SKILL.md

    PagerDuty MCP Tools & API Patterns

    Overview

    PagerDuty provides an official hosted MCP server at mcp.pagerduty.com (US) and mcp.eu.pagerduty.com (EU). The server exposes 66 tools generated from PagerDuty's REST API and is generally available to all PagerDuty accounts. When accessed through the MCP Gateway, credentials are injected automatically — no manual auth handling needed.

    Critical auth note: PagerDuty uses Token token=<key> header format, NOT Bearer. Using Bearer returns 401.

    Authentication

    Token Type and Header Format

    Authorization: Token token=<your-user-api-token>
    Token TypeWhere to GenerateScope
    User API Token (recommended)My Profile → User Settings → API Access → Create API User TokenYour user's permissions
    General Access TokenAdmin → API Access Keys → Create New API KeyFull account access (requires admin)

    User API tokens are preferred — they carry individual audit attribution and work for all 66 MCP tools.

    EU Region

    For EU PagerDuty accounts, the gateway operator sets VENDOR_URL_PAGERDUTY=https://mcp.eu.pagerduty.com. No change needed in your API token.

    How the Gateway Injects Credentials

    The MCP Gateway stores your token as an org credential and automatically forwards:

    Authorization: Token token=<stored-api-token>

    Complete MCP Tool Reference (66 Tools)

    Incidents (14 tools)

    ToolDescription
    list_incidentsList incidents with filters (status, urgency, service, team, date range)
    get_incidentGet full incident details by ID
    create_incidentCreate a new incident
    update_incidentUpdate incident fields (status, priority, urgency, title)
    merge_incidentsMerge duplicate incidents into one
    list_incident_alertsList alerts associated with an incident
    list_incident_notesList notes/comments on an incident
    create_incident_noteAdd a note to an incident
    list_incident_log_entriesList all log entries for an incident
    snooze_incidentSnooze an incident for a duration
    manage_incidentsBulk update multiple incidents
    list_past_incidentsList resolved incidents matching a pattern
    get_incident_field_valuesGet custom field values for an incident
    set_incident_field_valuesSet custom field values for an incident

    On-Call (1 tool)

    ToolDescription
    list_oncallsList current on-call entries (who is on-call for which schedule)

    Schedules (6 tools)

    ToolDescription
    list_schedulesList all on-call schedules
    get_scheduleGet schedule details with rotation layers
    create_scheduleCreate a new on-call schedule
    update_scheduleUpdate schedule details or layers
    delete_scheduleDelete a schedule
    list_schedule_overridesList temporary overrides for a schedule

    Escalation Policies (2 tools)

    ToolDescription
    list_escalation_policiesList all escalation policies
    get_escalation_policyGet escalation policy details and rules

    Services (4 tools)

    ToolDescription
    list_servicesList all services
    get_serviceGet service details
    create_serviceCreate a new service
    update_serviceUpdate service settings

    Event Orchestrations (7 tools)

    ToolDescription
    list_event_orchestrationsList all event orchestrations
    get_event_orchestrationGet orchestration details
    get_global_orchestration_rulesGet global routing rules
    update_global_orchestration_rulesUpdate global routing rules
    get_service_orchestration_rulesGet per-service routing rules
    update_service_orchestration_rulesUpdate per-service routing rules
    get_event_orchestration_active_statusCheck if orchestration is active

    Status Pages (8 tools)

    ToolDescription
    list_status_pagesList all status pages
    get_status_pageGet status page details
    list_status_page_postsList incident posts on a status page
    create_status_page_postCreate a new status page post
    update_status_page_postUpdate an existing post
    delete_status_page_postDelete a status page post
    list_status_page_post_updatesList updates for a post
    create_status_page_post_updateAdd update to an existing post

    Teams (7 tools)

    ToolDescription
    list_teamsList all teams
    get_teamGet team details
    create_teamCreate a team
    update_teamUpdate team details
    delete_teamDelete a team
    list_team_membersList members of a team
    add_team_memberAdd a user to a team

    Users (2 tools)

    ToolDescription
    list_usersList all users in the account
    get_userGet user details and contact methods

    Alert Grouping (5 tools)

    ToolDescription
    get_alert_grouping_settingsGet alert grouping configuration for a service
    update_alert_grouping_settingsUpdate alert grouping settings
    list_intelligent_alert_grouping_settingsList AI-based alert grouping configs
    create_intelligent_alert_grouping_settingsConfigure AI-based grouping for a service
    update_intelligent_alert_grouping_settingsUpdate AI-based grouping settings

    Incident Workflows (3 tools)

    ToolDescription
    list_incident_workflowsList all incident workflow automation rules
    get_incident_workflowGet workflow details and triggers
    list_incident_workflow_instancesList workflow executions for an incident

    Change Events (3 tools)

    ToolDescription
    list_change_eventsList change events (deployments, config changes)
    get_change_eventGet change event details
    update_change_eventUpdate a change event

    Log Entries (2 tools)

    ToolDescription
    list_log_entriesList log entries across the account
    get_log_entryGet a specific log entry

    Pagination

    PagerDuty uses offset-based pagination with limit and offset parameters:

    ParameterDescriptionDefault
    limitResults per page (max 100)25
    offsetNumber of results to skip0
    totalInclude total count in responsefalse

    Pattern:

    1. Call tool with limit=100, offset=0
    2. Check response.more — if true, fetch next page with offset=100
    3. Continue until response.more is false

    Common Filter Parameters

    Most list tools support these standard filters:

    ParameterDescription
    team_ids[]Filter to specific teams
    service_ids[]Filter to specific services
    user_ids[]Filter to specific users
    sinceStart time (ISO 8601)
    untilEnd time (ISO 8601)
    statuses[]Filter by status values

    Error Handling

    HTTP CodeCauseResolution
    401Invalid or missing tokenVerify token; use Token token= format, not Bearer
    403Insufficient permissionsCheck user role; some tools require Account Owner
    404Resource not foundVerify the ID exists with a list call first
    429Rate limitedBack off 60 seconds; PagerDuty limits 900 req/min
    500PagerDuty internal errorRetry once; check PagerDuty status page

    Best Practices

    1. Filter server-side — Use team_ids[] and service_ids[] to scope results
    2. Paginate with limit=100 — Max allowed; reduces round trips for large accounts
    3. Use since/until for incident queries — Avoid unbounded queries on large accounts
    4. List before get — Always list to find IDs before calling single-resource get tools

    Related Skills

    Frequently asked questions

    What to verify before installation and use

    What does the PagerDuty API Patterns source document cover?

    PagerDuty API and hosted MCP fundamentals: US/EU MCP endpoints, the `Token token=` auth header and token types, the complete 66-tool reference across 13 categories (incidents, on-call, schedules, escalation policies, services, event orchestrations, status pages, teams, users, and more), offset pagination, common filter parameters, rate limits, and error cod…

    How do I install PagerDuty API Patterns?

    The source record exposes this install command: npx skills add https://github.com/WYRE-AI/msp-claude-plugins --skill "msp-claude-plugins/pagerduty/pagerduty/skills/api-patterns". Inspect the command and pinned source before running it.

    Alternatives

    Compare before choosing

    Computed 10029,236

    garrytan/gbrain

    bulk-ingestion

    End-to-end discipline for turning any large data source (audio libraries, email takeouts, document corpora, chat exports, API dumps) into brain pages at scale. The lifecycle spine: SCHEMA → ACCESS → TRIAL → EVALUATE → IMPROVE → CODIFY → TEST → SKILLIFY → BULK → MONITOR. State is tracked in a durable JSON manifest (see MANIFEST-PATTERN.md) so any crash, session boundary, or subagent fan-out resumes from ground truth instead of memory.

    2026-08-280 platforms
    Computed 10025,136

    alirezarezvani/claude-skills

    app-store-optimization

    App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store. Use when the user asks about ASO, app store rankings, app metadata, app titles and descriptions, app store listings, app visibility, or mobile app marketing on iOS or Android. Supports keyword research and scoring, competitor keyword analysis, metadata optimization, A/B test planning, launch checklist

    2026-08-260 platforms
    Computed 1005,277

    dotnet/skills

    migrate-vstest-to-mtp

    Migrates .NET test projects from VSTest to Microsoft.Testing.Platform (MTP). Use when user asks to "migrate to MTP", "switch from VSTest", "enable Microsoft.Testing.Platform", "use MTP runner", set OutputType=Exe only for test projects in Directory.Build.props, or mentions EnableMSTestRunner, EnableNUnitRunner, or UseMicrosoftTestingPlatformRunner. USE FOR: MTP behavioral differences vs VSTest (exit code 8, zero tests discovered, --ignore-exit-code, TESTINGPLATFORM_EXITCODE_IGNORE); centralizing

    2026-08-280 platforms
    Computed 100147

    oaustegard/claude-skills

    featuring

    Generate hierarchical _FEATURES.md files that describe what a codebase DOES from a user/consumer perspective, anchored to source symbols via tree-sitting. Supports large complex codebases through feature-driven decomposition into sub-feature files. Uses a multi-pass synthesis: orientation → detail → overview rewrite. Use when someone says "what does this do", "document features", "feature inventory", "_FEATURES.md", or needs to understand a codebase's purpose before modifying it. Complements tre

    2026-08-281 platforms