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
- In Paperclip, open Connectors and select PagerDuty.
- On the Access step, choose the identity and which agents may use the connection.
- Choose US service region or EU service region, then paste a PagerDuty user API token.
PagerDuty tools for agents18
Write 18
browse_activitylist_log_entries, get_log_entry
browse_alert_groupinglist, get
browse_change_eventslist, get, list_service
browse_escalation_policieslist, get
browse_event_orchestrationslist, get, get_router, get_service, get_global
browse_incidentslist, get, list_alerts, get_alert, list_notes, context (related|past|outlier), list_change_events, list_workflows, get_workflow
Show all 18 Write tools
Write tools 7–18
browse_scheduleslist, get, list_users, list_oncalls
browse_serviceslist, get
browse_status_pageslist, list_severities, list_impacts, list_statuses, get_post, list_post_updates
browse_teamslist, get, list_members
browse_userslist, get
manage_alert_groupingcreate, update, delete
manage_event_orchestrationsupdate_router, append_router_rule
manage_incidentscreate, update, add_note, add_responders, start_workflow
manage_schedulescreate, update, create_override
manage_servicescreate, update
manage_status_pagescreate_post, create_post_update
manage_teamscreate, update, delete, add_member, remove_member
Tool availability and permissions
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.
