---
title: "Update a PagerDuty MCP integration."
method: PUT
path: "/v1/integrations/pagerduty-mcp/{id}"
tags: ["PagerDuty MCP Integration"]
---

# Update a PagerDuty MCP integration.

`PUT /v1/integrations/pagerduty-mcp/{id}`

## Request

- Base URL: `https://docs.grepr.ai` (the document declares no server; this is the origin it was published from)
- URL: `https://docs.grepr.ai/v1/integrations/pagerduty-mcp/{id}`
- Auth: one of:
  - API key in header `GREPR-API-KEY`
  - OpenID Connect (`https://grepr-prod.us.auth0.com/.well-known/openid-configuration`)

Updates a PagerDuty MCP integration. The version should be increased by one for every new update in order for the write to succeed. Otherwise, a '409 Conflict' will be returned.

## Path parameters

- `id` string, required

## Request body

- WritePagerDutyMcp
  - `name` string, required: Name of the integration.
  - `payload` PagerDutyMcp, required: The payload containing integration data.
    - `accountUrl` string: Base web URL of the PagerDuty account, used to link to created incidents (e.g. https://acme.pagerduty.com). Optional.
    - `apiKey` string: Masked API key for the MCP server.
    - `serverUrl` string, required: MCP server endpoint URL.
    - `validateKeysOnSave` boolean: Indicates whether to validate the API key when saving.
  - `teamIds` string[]: The team IDs that this integration is associated with.
  - `type` 'pagerduty-mcp', required: The type of the integration. This is used to determine the payload type.
  - `version` integer, required: Version of the integration. Should be increased by one for every new update in order for the write to succeed. Otherwise, a '409 Conflict' will be returned.

## Response `200`

Integration updated successfully

- ReadPagerDutyMcp
  - `createdAt` string, date-time, required: Timestamp when the integration was created.
  - `id` string, required: The integration id
  - `jobIds` string[], required: List of job IDs associated with the integration.
  - `name` string, required: Name of the integration.
  - `organizationId` string, required: Organization ID of the integration.
  - `payload` PagerDutyMcp, required: The payload containing integration data.
    - `accountUrl` string: Base web URL of the PagerDuty account, used to link to created incidents (e.g. https://acme.pagerduty.com). Optional.
    - `apiKey` string: Masked API key for the MCP server.
    - `serverUrl` string, required: MCP server endpoint URL.
    - `validateKeysOnSave` boolean: Indicates whether to validate the API key when saving.
  - `teamIds` string[]: The team IDs that this integration is associated with.
  - `type` 'pagerduty-mcp', required: The type of the integration. This is used to determine the payload type.
  - `updatedAt` string, date-time, required: Timestamp when the integration was last updated.
  - `version` integer, required: Version of the integration. Should be increased by one for every new update in order for the write to succeed. Otherwise, a '409 Conflict' will be returned.

## Other responses

- `401`: Unauthorized
- `404`: Integration not found.
- `409`: Integration was modified or deleted concurrently.

---

[API](https://skmtc.dev/grepr/apis/grepr-api.md) - [All operations](https://skmtc.dev/grepr/apis/grepr-api/llms.txt) - [OpenAPI document](https://skmtc.dev/grepr/apis/grepr-api/revisions/2a5ce03a0bf0?raw)
