II.
ToolServer JSON
Structured · livetool-server:mcp-pagerduty
PagerDuty MCP Server json
Inspect the normalized record payload exactly as the atlas UI reads it.
{
"id": "tool-server:mcp-pagerduty",
"_kind": "ToolServer",
"_file": "extensions/tool-servers/mcp-monitoring.yaml",
"_cluster": "extensions",
"attributes": {
"displayName": "PagerDuty MCP Server",
"description": "MCP server providing access to PagerDuty incident management.\nEnables AI agents to list and acknowledge incidents, manage on-call\nschedules, trigger alerts, and coordinate incident response workflows.\n",
"protocol": "mcp",
"category": "monitoring",
"repoUrl": "https://github.com/PagerDuty/mcp-server-pagerduty",
"maintainer": "PagerDuty",
"mcpTransports": [
"mcp-transport:stdio"
]
},
"outgoingEdges": [
{
"from": "tool-server:mcp-pagerduty",
"to": "responsibility:incident-response-coordination",
"kind": "supports_work",
"attributes": {
"confidence": "high",
"evidence": "PagerDuty incident and schedule access directly supports response coordination."
}
},
{
"from": "tool-server:mcp-pagerduty",
"to": "workflow:on-call-rotation-management",
"kind": "supports_work",
"attributes": {
"confidence": "high",
"evidence": "On-call schedules, escalations, and incidents are PagerDuty-native workflow surfaces."
}
},
{
"from": "tool-server:mcp-pagerduty",
"to": "workflow:incident-response",
"kind": "supports_work",
"attributes": {
"confidence": "high",
"evidence": "Incident acknowledgement, escalation, and coordination are response-critical actions."
}
},
{
"from": "tool-server:mcp-pagerduty",
"to": "tool:pagerduty",
"kind": "integrates_with",
"attributes": {}
},
{
"from": "tool-server:mcp-pagerduty",
"to": "domain:observability",
"kind": "lib_applies_to_domain",
"attributes": {}
},
{
"from": "tool-server:mcp-pagerduty",
"to": "domain:devops",
"kind": "lib_applies_to_domain",
"attributes": {}
}
],
"incomingEdges": []
}