A server that exposes PagerDuty API functionality to LLMs with structured inputs and outputs, enabling management of incidents, services, teams, and users.
A community-maintained MCP server for interacting with PagerDuty accounts, enabling management of incidents, services, schedules, and event orchestrations through MCP-enabled clients.
Bind external systems (ticketing, alerts, Slack, monitors) to FleetQ so events become signals that trigger rules and agents. Query and extend the knowledge graph for agent reasoning.
Constructs a user context dictionary containing user, team, service, and escalation policy IDs to filter PagerDuty resources like incidents, services, and teams.