Kiwi

Kiwi for PagerDuty

Have the agent on a Kiwi step read a PagerDuty incident, add its findings as a note and find who is on call, through PagerDuty's MCP server.

  • Your agent works in PagerDuty through its own connection. Kiwi does not call PagerDuty and never holds its credentials.
  • A workflow skill can list PagerDuty among the tools it requires. When you supply your agent's available tools to a skill check and PagerDuty is not among them, the check reports SK15-UNSUPPORTED-TOOL.
  • A project Admin can add links to PagerDuty, with notes, under Connections and bind them to the steps that use them. The agent reads them with list_connections.
  • The agent can report the tools and plugins it ran with, including its PagerDuty connection, with report_configuration.
  • The agent submits links to its work in PagerDuty as the step's outputs. People review them, and sign-off stays with the people your workflow names.

What your agent can do in PagerDuty

  • List incidents and read the details of one incident.
  • Add a note to an incident or add responders to it.
  • Find who is on call for a schedule or escalation policy.
  • Read services and the change events recorded against them.

Set up

  1. Connect your agent to Kiwi

    Add Kiwi's hosted MCP server, https://kiwiflow.io/mcp, to your coding agent.

  2. Connect your agent to PagerDuty

    Add the PagerDuty MCP server to your agent with this URL. The credentials stay with your agent.

    https://mcp.pagerduty.com/mcp
  3. Example skill

    Publish instructions like these as a workflow skill that lists PagerDuty among its required tools.

    Start from the PagerDuty incident ID in the step's assignment.
    Read the incident and the recent change events of its service in PagerDuty.
    Add a note to the incident with your findings.
    Submit the note text and any related pull request links as the outputs.
    Do not resolve or reassign the incident; the run's Owner decides that.
    If you cannot read the incident, report a blocker.