# PagerDuty connector

[Product](https://paperclip.ing/product/) / [Connectors](https://paperclip.ing/product/connectors/) / PagerDuty

Inspect incidents, check schedules and update incidents.

Category: [Developer tools](/product/connectors/?category=developer)
Tools from: [PagerDuty](https://support.pagerduty.com/main/docs/pagerduty-mcp-server)
Sign-in: Choose a supported connection method
Works as: Agent tool

Source recorded: Sep 30, 2026

## Overview

Paperclip’s PagerDuty MCP connector gives your AI agents tools to inspect incidents, check schedules and update incidents. Each tool can be Allowed, Ask first or Off.

Reach follows the token owner’s PagerDuty role and team access in the selected service region.

## What agents can do with PagerDuty

- Investigate incidents and service context (`browse_incidents`, `browse_services`)
- Check on-call schedules and users (`browse_schedules`, `browse_users`)
- Review an incident before updating it (`browse_incidents`, `manage_incidents`)

## How to connect PagerDuty

1. In Paperclip, open Connectors and select PagerDuty.
2. On the Access step, choose the identity and which agents may use the connection.
3. Choose US service region or EU service region, then paste a PagerDuty user API token.

[Setup guide](https://docs.paperclip.ing/connectors/pagerduty/)

## PagerDuty tools for agents (18)



### Write (18)

<div data-tool-name="browse_activity" data-tool-class="write">
<code>browse_activity</code>
<p class="c4-description-summary">list_log_entries, get_log_entry</p>
</div>

<div data-tool-name="browse_alert_grouping" data-tool-class="write">
<code>browse_alert_grouping</code>
<p class="c4-description-summary">list, get</p>
</div>

<div data-tool-name="browse_change_events" data-tool-class="write">
<code>browse_change_events</code>
<p class="c4-description-summary">list, get, list_service</p>
</div>

<div data-tool-name="browse_escalation_policies" data-tool-class="write">
<code>browse_escalation_policies</code>
<p class="c4-description-summary">list, get</p>
</div>

<div data-tool-name="browse_event_orchestrations" data-tool-class="write">
<code>browse_event_orchestrations</code>
<p class="c4-description-summary">list, get, get_router, get_service, get_global</p>
</div>

<div data-tool-name="browse_incidents" data-tool-class="write">
<code>browse_incidents</code>
<p class="c4-description-summary">list, get, list_alerts, get_alert, list_notes, context (related|past|outlier), list_change_events, list_workflows, get_workflow</p>
</div>

<div data-tool-name="browse_schedules" data-tool-class="write">
<code>browse_schedules</code>
<p class="c4-description-summary">list, get, list_users, list_oncalls</p>
</div>

<div data-tool-name="browse_services" data-tool-class="write">
<code>browse_services</code>
<p class="c4-description-summary">list, get</p>
</div>

<div data-tool-name="browse_status_pages" data-tool-class="write">
<code>browse_status_pages</code>
<p class="c4-description-summary">list, list_severities, list_impacts, list_statuses, get_post, list_post_updates</p>
</div>

<div data-tool-name="browse_teams" data-tool-class="write">
<code>browse_teams</code>
<p class="c4-description-summary">list, get, list_members</p>
</div>

<div data-tool-name="browse_users" data-tool-class="write">
<code>browse_users</code>
<p class="c4-description-summary">list, get</p>
</div>

<div data-tool-name="manage_alert_grouping" data-tool-class="write">
<code>manage_alert_grouping</code>
<p class="c4-description-summary">create, update, delete</p>
</div>

<div data-tool-name="manage_event_orchestrations" data-tool-class="write">
<code>manage_event_orchestrations</code>
<p class="c4-description-summary">update_router, append_router_rule</p>
</div>

<div data-tool-name="manage_incidents" data-tool-class="write">
<code>manage_incidents</code>
<p class="c4-description-summary">create, update, add_note, add_responders, start_workflow</p>
</div>

<div data-tool-name="manage_schedules" data-tool-class="write">
<code>manage_schedules</code>
<p class="c4-description-summary">create, update, create_override</p>
</div>

<div data-tool-name="manage_services" data-tool-class="write">
<code>manage_services</code>
<p class="c4-description-summary">create, update</p>
</div>

<div data-tool-name="manage_status_pages" data-tool-class="write">
<code>manage_status_pages</code>
<p class="c4-description-summary">create_post, create_post_update</p>
</div>

<div data-tool-name="manage_teams" data-tool-class="write">
<code>manage_teams</code>
<p class="c4-description-summary">create, update, delete, add_member, remove_member</p>
</div>

This list describes the reviewed tools. Your selected method, provider access and action permissions determine what agents can use.

These lists use a conservative permission policy. Read requires a provider read-only hint or a reviewed Paperclip read rule. Evidence that an action changes data or submits information elsewhere puts it in Write. Write also includes actions we cannot verify as read-only. Read describes the reviewed evidence; it does not guarantee that an action has no side effects. A connected account can group actions differently.

The provider supplies tool names and the actions each tool supports. The published action lists appear as descriptions; individual actions are not separate tools.



### Connection policies

Discovered actions follow the connection’s policies. Review their permissions and set actions to Ask first or Off as needed. Incident changes can affect on-call responders. Require approval for changes.

## PagerDuty connector FAQ

### Can I require approval for actions?

Set an action to Ask first to require human approval of each call or Off to prevent calls. Allowed actions run without approval. Read and Write grouping is separate from these settings.

### What can agents reach in PagerDuty?

Reach follows the token owner’s PagerDuty role and team access in the selected service region.

### What do I need before connecting?

Create a user API token under the intended PagerDuty account. A general account-wide REST API key is not the credential this setup expects.


Ways to connect

- US service region
  - Paste a PagerDuty user API token for an account in the US service region.
- EU service region
  - Paste a PagerDuty user API token for an account in the EU service region.

[PagerDuty connector](https://docs.paperclip.ing/connectors/pagerduty/)

[Set action permissions](https://docs.paperclip.ing/connectors/action-permissions/)

## Related connectors

- [Cloudflare](https://paperclip.ing/product/connectors/cloudflare/): Find API operations and execute resource changes.
- [GitHub](https://paperclip.ing/product/connectors/github/): Read code and pull requests, comment on issues.
- [Netlify](https://paperclip.ing/product/connectors/netlify/): Inspect projects and deploys and start deployments.

## Give your agents PagerDuty.

Join the Paperclip waitlist to connect PagerDuty and choose what your agents can do.

[Join the waitlist](https://paperclip.ing/waitlist/)