Home / Servers / PagerDuty API / migrate_orchestration_integration
Migrate an Integration from one Event Orchestration to another
An MCP tool from the PagerDuty API server, hosted on mcp.hjlabs.in.
Migrate an Integration from one Event Orchestration to another Move an Integration and its Routing Key from the Event Orchestration specified in the request payload, to the Event Orchestration specified in the request URL. Any future events sent to this… [POST /event_orchestrations/{id}/integrations/migration]
Name on the gateway: pagerduty_api__migrate_orchestration_integration · may change things.
Parameters
| Name | Type | Description |
|---|---|---|
id required | string | The ID of an Event Orchestration. |
source_id required | string | The ID of the Event Orchestration you'll be moving the Integration away from |
source_type required | orchestration | The type of of the source_id object |
integration_id required | string | The ID of the Integration you'll be moving |
How to call it
Through the Smart Gateway, any client can run it by name with call_tool, or let the gateway find it with search_tools:
{
"name": "pagerduty_api__migrate_orchestration_integration",
"arguments": {
"id": "…",
"source_id": "…",
"source_type": "…",
"integration_id": "…"
}
}Or connect the PagerDuty API server directly, which lists 459 tools including this one:
claude mcp add --transport http hj-pagerduty-api https://mcp.hjlabs.in/mcp/pagerduty-api \
--header "Authorization: Bearer YOUR_API_KEY"Try asking
Use the migrate an integration from one event orchestration to another tool with id set to ….