Read service and incident summaries with your PagerDuty REST API key. Select a read-only key and enable only the commands you need. One explicit page or incident per call, without retries or background polling. Incident bodies, assignments, contacts, integrations, routing keys and write actions are excluded. Events API routing keys do not authenticate these REST commands.
What you can do (3)
What you can do
Available commands: 3 (3 read, 0 write). Enable only the commands your application needs.
| Command | Effect |
|---|---|
List service summaries — pagerduty.services.list |
Read |
List incident summaries — pagerduty.incidents.list |
Read |
Get an incident summary — pagerduty.incidents.get |
Read |
Connect and use
Open the integration's connection form to check the available credential source. The source has not been resolved for this documentation export. The instructions below apply when using your own provider account.
Get your provider credentials
Follow these steps for PagerDuty, then enter the issued values in the connection form below.
- In PagerDuty open Integrations > Developer Tools > API Access Keys. An Admin or Account Owner can create a general-access REST API key; select Read-only API Key and copy it when shown. Enter it in PagerDuty REST API key in this connection, choose only required commands and save. An Events API integration/routing key is not a REST API key. Start with services.list; incidents.list requires an explicit since/until window (at most six months under PagerDuty rules), limit and offset. Each invocation reads one page without retries or polling. This subset returns summaries only and excludes incident bodies, contacts and writes.
Where to enter credentials
In the integration page, sign in, choose your workspace and open Connect. If a Credentials choice is shown, select Use my credentials. Fill the following connection fields and save. Provider credentials belong in this form, never in an MCP configuration or tool input.
| Connection field | Requirement |
|---|---|
| PagerDuty REST API key | Required |
Open API keys and create a Tooluse.net key for the enabled commands.
Set TOOLUSE_API_KEY in your client and use the shared MCP configuration.
Configure Claude Code, Codex or Cursor once
Permissions and results
If you have more than one workspace, check the selected workspace in the connection or API-key dialog before saving. Roles, enabled commands, expiry and revocation use Tooluse.net's existing permissions. Disabling a connection or revoking a key immediately prevents new calls.
Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.
Your connection's daily allowance and key permissions also apply. Adding a connection does not make a provider request.
Calls return the shared execution receipt and a Claude tool_result. Provider output varies by operation; consult the provider documentation for its response fields. Unconfirmed calls should be checked before retrying.
Call from your client
Use the shared MCP configuration. Refresh your client's tool list after saving the connection or changing key permissions, then call the returned tool name with the example input below.
Configure Claude Code, Codex or Cursor once
Discover your enabled tools
List permitted tools in Claude format. Read every page using page and size (maximum 100) until all results have been received. Use the returned name, not a catalog capability identifier, in the tool_use block.
curl 'https://api.tooluse.net/v1/tools' \
-H "Authorization: Bearer $TOOLUSE_API_KEY"
Find this command in the tool list permitted by your key. Replace svc_FROM_YOUR_TOOL_LIST with its returned name. Use a new Idempotency-Key for each new call and retain it when retrying that same call.
HTTP call
curl 'https://api.tooluse.net/v1/tool-calls' \
-H "Authorization: Bearer $TOOLUSE_API_KEY" \
-H 'Content-Type: application/json' \
-H 'Idempotency-Key: replace-with-a-new-call-id' \
--data '{
"type": "tool_use",
"id": "toolu_example",
"name": "svc_FROM_YOUR_TOOL_LIST",
"input": {
"query": {
"limit": 20,
"offset": 0
}
}
}'
Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.
Commands
List service summaries — pagerduty.services.list
Read one page of service IDs, names, states and timestamps visible to your REST API key. Integration/routing keys, escalation policies and contacts are excluded.
This is a read operation. Provider rate limits and data access rules still apply.
Parameters
Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.
| Parameter | Type | Required in parent | Description | Constraints |
|---|---|---|---|---|
query |
object | Required | additionalProperties: false |
|
query.limit |
integer | Required | Maximum number of summaries in this explicit page. | minimum: 1; maximum: 100 |
query.offset |
integer | Required | Offset of this page. Follow the returned more flag explicitly; no automatic pagination. | minimum: 0; maximum: 10000 |
Full JSON Schema
Example input
{
"query": {
"limit": 20,
"offset": 0
}
}
At most 1 provider requests per invocation; timeout: 30 seconds.
List incident summaries — pagerduty.incidents.list
Read one explicit page of incident summaries within your since/until window. PagerDuty allows a maximum six-month window. Incident bodies, assignments, responders and contact details are excluded. Follow the returned more flag explicitly.
This is a read operation. Provider rate limits and data access rules still apply.
Parameters
Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.
| Parameter | Type | Required in parent | Description | Constraints |
|---|---|---|---|---|
query |
object | Required | additionalProperties: false |
|
query.limit |
integer | Required | Maximum number of summaries in this explicit page. | minimum: 1; maximum: 100 |
query.offset |
integer | Required | Offset of this page. Follow the returned more flag explicitly; no automatic pagination. | minimum: 0; maximum: 10000 |
query.since |
string | Required | Inclusive start of the incident search window. | format: "date-time" |
query.until |
string | Required | End of the search window, at or after since; at most six months under provider rules. | format: "date-time" |
Full JSON Schema
Example input
{
"query": {
"limit": 20,
"offset": 0,
"since": "2026-11-01T00:00:00Z",
"until": "2026-11-02T00:00:00Z"
}
}
At most 1 provider requests per invocation; timeout: 30 seconds.
Get an incident summary — pagerduty.incidents.get
Read the ID, number, title, state, urgency and timestamps of one incident accessible to your REST API key. This does not return incident bodies, notes, responders, assignments, contacts or routing credentials.
This is a read operation. Provider rate limits and data access rules still apply.
Parameters
Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.
| Parameter | Type | Required in parent | Description | Constraints |
|---|---|---|---|---|
path |
object | Required | additionalProperties: false |
|
path.id |
string | Required | PagerDuty incident ID, such as PABC123. | pattern: "^[A-Z0-9]{6,32}$" |
Full JSON Schema
Example input
{
"path": {
"id": "PABC123"
}
}
At most 1 provider requests per invocation; timeout: 30 seconds.
Errors
Check the key's expiry, revocation, workspace and allowed operations.
Reuse the same idempotency key only for the same request.
The connection or provider limit has been reached. Check the receipt before retrying.
Test the connection
Open the integration's commands below to inspect parameters and examples. Start with a read command for an account or resource you can access. Refresh your client's tool list, use the returned tool name, and check the execution result and usage. Provider charges and permissions still apply. Never test a write against production data without reviewing it.