> ## Documentation Index
> Fetch the complete documentation index at: https://www.truefoundry.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Set up PagerDuty MCP Server

> Connect PagerDuty's hosted MCP server to TrueFoundry with per-user API tokens.

PagerDuty's hosted MCP server lets agents inspect and manage incidents, on-call schedules, services, and workflows. It uses User API Tokens and the `Authorization: Token <token>` header format.

## Prerequisites

* A TrueFoundry account with permission to add MCP servers.
* A PagerDuty account with Advanced Permissions enabled.

## Register in TrueFoundry

Add a remote MCP server with the correct regional URL:

| Region | URL                                |
| ------ | ---------------------------------- |
| US     | `https://mcp.pagerduty.com/mcp`    |
| EU     | `https://mcp.eu.pagerduty.com/mcp` |

Configure API Key authentication with **Individual Credentials**:

| Field            | Value               |
| ---------------- | ------------------- |
| **Header name**  | `Authorization`     |
| **Header value** | `Token {{API_KEY}}` |

Users then add their PagerDuty token in **Auth Overrides**.

## Generate a PagerDuty Token

Each user opens **My Profile** > **User Settings** > **API Access**, creates an **API User Token**, and copies it immediately. Paste only the token value into the TrueFoundry auth override.

## Security Notes

PagerDuty User API Tokens inherit the user's role and do not expire automatically. Rotate them periodically and expose incident mutation tools only to users who should be able to update live incidents.