Skip to main content
PagerDuty operates in multiple regions with separate API endpoints. This guide explains how to configure the MCP server to connect to the correct regional endpoint for your account.

​
Understanding PagerDuty Regions

PagerDuty has two primary regions:

US Region

API Endpoint: https://api.pagerduty.comThis is the default region and is used by most PagerDuty accounts.

EU Region

API Endpoint: https://api.eu.pagerduty.comUsed by accounts based in the European Union.

​
Default Configuration

By default, the PagerDuty MCP Server connects to the US region API endpoint (https://api.pagerduty.com). If your account is in the US region, you don’t need to configure anything.
The default endpoint is set in the server’s ApplicationContextStrategy class at pagerduty_mcp/context/application_context_strategy.py:21.

​
Determining Your Region

To determine which region your PagerDuty account is in:
  1. Log in to your PagerDuty account
  2. Check the URL in your browser:
    • If it’s *.pagerduty.com, you’re in the US region
    • If it’s *.eu.pagerduty.com, you’re in the EU region
Alternatively, contact your PagerDuty administrator if you’re unsure about your account’s region.

​
Configuring Regional Endpoints

To configure a different API endpoint, set the PAGERDUTY_API_HOST environment variable when starting the MCP server.

​
VS Code

settings.json
{
  "mcp": {
    "servers": {
      "pagerduty-mcp": {
        "type": "stdio",
        "command": "uvx",
        "args": ["pagerduty-mcp", "--enable-write-tools"],
        "env": {
          "PAGERDUTY_USER_API_KEY": "${input:pagerduty-api-key}",
          "PAGERDUTY_API_HOST": "https://api.eu.pagerduty.com"
        }
      }
    }
  }
}

​
Cursor

settings.json
{
  "mcpServers": {
    "pagerduty-mcp": {
      "type": "stdio",
      "command": "uvx",
      "args": ["pagerduty-mcp", "--enable-write-tools"],
      "env": {
        "PAGERDUTY_USER_API_KEY": "${input:pagerduty-api-key}",
        "PAGERDUTY_API_HOST": "https://api.eu.pagerduty.com"
      }
    }
  }
}

​
Claude Desktop

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "pagerduty-mcp": {
      "command": "uvx",
      "args": ["pagerduty-mcp", "--enable-write-tools"],
      "env": {
        "PAGERDUTY_USER_API_KEY": "your-pagerduty-api-key-here",
        "PAGERDUTY_API_HOST": "https://api.eu.pagerduty.com"
      }
    }
  }
}

​
Docker

Pass the regional endpoint as an environment variable: 
docker run -i --rm \
  -e PAGERDUTY_USER_API_KEY="your-api-key-here" \
  -e PAGERDUTY_API_HOST="https://api.eu.pagerduty.com" \
  pagerduty-mcp:latest --enable-write-tools

​
Local Development

settings.json
{
  "mcp": {
    "servers": {
      "pagerduty-mcp": {
        "type": "stdio",
        "command": "uv",
        "args": [
          "run",
          "--directory",
          "/path/to/pagerduty-mcp",
          "python",
          "-m",
          "pagerduty_mcp",
          "--enable-write-tools"
        ],
        "env": {
          "PAGERDUTY_USER_API_KEY": "${input:pagerduty-api-key}",
          "PAGERDUTY_API_HOST": "https://api.eu.pagerduty.com"
        }
      }
    }
  }
}

​
Regional Considerations

Data in EU region accounts is stored and processed within the European Union to comply with GDPR and other regional data protection regulations.
API tokens are region-specific. A token generated in the US region will not work with the EU API endpoint and vice versa.
Both regions offer the same features and API capabilities. Regional endpoints are designed for data residency compliance, not feature differences.
Using the correct regional endpoint may provide better performance due to geographic proximity to the data centers.

​
Troubleshooting Regional Endpoint Issues

You may be using a token from one region with the API endpoint of another region. Verify that:
  • Your token was generated in the same region as the API endpoint you’re using
  • The PAGERDUTY_API_HOST matches your account’s region
Double-check the PAGERDUTY_API_HOST value for typos. The correct values are:
  • US: https://api.pagerduty.com
  • EU: https://api.eu.pagerduty.com
Note the protocol (https://) is required.
If you’re unsure about your region:
  1. Try the default US endpoint first
  2. If you get authentication errors with a valid token, try the EU endpoint
  3. Check with your PagerDuty administrator
  4. Look at your PagerDuty web URL - it will indicate the region

​
Configuration Examples

​
US Region (Default)

For US region accounts, you can omit the PAGERDUTY_API_HOST variable entirely: 
{
  "env": {
    "PAGERDUTY_USER_API_KEY": "your-api-key-here"
  }
}
Or explicitly set it: 
{
  "env": {
    "PAGERDUTY_USER_API_KEY": "your-api-key-here",
    "PAGERDUTY_API_HOST": "https://api.pagerduty.com"
  }
}

​
EU Region

For EU region accounts, you must set the PAGERDUTY_API_HOST variable: 
{
  "env": {
    "PAGERDUTY_USER_API_KEY": "your-api-key-here",
    "PAGERDUTY_API_HOST": "https://api.eu.pagerduty.com"
  }
}

​
How It Works

The MCP server’s create_pd_client() function reads the PAGERDUTY_API_HOST environment variable and configures the PagerDuty API client accordingly: 
def create_pd_client() -> RestApiV2Client:
    """Create a PagerDuty client."""
    api_key = os.getenv("PAGERDUTY_USER_API_KEY")
    api_host = os.getenv("PAGERDUTY_API_HOST", "https://api.pagerduty.com")

    if not api_key:
        raise RuntimeError("An API key is required to call the PagerDuty API.")

    pd_client = PagerdutyMCPClient(api_key)
    if api_host:
        pd_client.url = api_host
    return pd_client
This implementation is in pagerduty_mcp/context/application_context_strategy.py:18-29.

​
Next Steps

API Authentication

Set up your PagerDuty API token

Write Mode

Learn about read-only vs write operations

Client Integration

Configure your MCP client

Troubleshooting

Get help with common issues

Build docs developers (and LLMs) love

Get started for freeTalk to us