Kiwi for incident.io
Have the agent on a Kiwi step read an incident.io incident, post updates to it and create follow-ups, through incident.io's remote MCP server.
- Your agent works in incident.io through its own connection. Kiwi does not call incident.io and never holds its credentials.
- A workflow skill can list incident.io among the tools it requires. When you supply your agent's available tools to a skill check and incident.io is not among them, the check reports
SK15-UNSUPPORTED-TOOL. - A project Admin can add links to incident.io, 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 incident.io connection, with
report_configuration. - The agent submits links to its work in incident.io as the step's outputs. People review them, and sign-off stays with the people your workflow names.
What your agent can do in incident.io
- List incidents and read the details of one.
- Post a message to an incident or update its fields.
- List and create the follow-ups of an incident.
- Read alerts, escalation paths and on-call schedules.
- Draft a status page update for a person to publish.
Set up
Connect your agent to Kiwi
Add Kiwi's hosted MCP server,
https://kiwiflow.io/mcp, to your coding agent.Connect your agent to incident.io
Add the incident.io MCP server to your agent with this URL. The credentials stay with your agent.
https://mcp.incident.io/mcpExample skill
Publish instructions like these as a workflow skill that lists incident.io among its required tools.
Read the incident.io incident ID from the step's assignment. Read the incident and its alerts in incident.io. Create a follow-up for each code change the incident needs, naming the repository and the file. Submit the follow-up links and related pull request links as outputs. Leave status page updates and closing the incident to the run's Owner. Report a blocker if you cannot read the incident.