Streamline incident response by searching, creating, and updating incidents, viewing alerts, and managing users directly from your workflows. Incident.io helps your team coordinate faster with clear visibility into status and severity, plus flexible ways to act on the data you retrieve.
Create and update incidents, or search incidents and alerts using powerful filters like status, severity, type, and date ranges.

​
What is Incident.io MCP?

The Incident.io MCP creates a customized node that understands the Incident.io integration so you can interact with it using natural language. Describe what you want, and the node returns structured data you can pass to the next step. This makes it easy to build repeatable workflows that query and update incidents without writing code.

​
What Can It Do for You?

  • Find incidents by status, severity, type, or date ranges and return only the fields you need
  • Create new incidents with the details you provide, including Slack-connected workflows
  • Update incident status and severity to keep response information current
  • List alerts and incident-alert links for better context and triage
  • Retrieve user lists or find specific users to route ownership and communication

​
Available Tools

ToolWhat It DoesExample Use
List UsersList users in your Incident.io account or get a specific user by ID with filtering options”Find users matching search term and return structured data with id, name, and email”
List IncidentsList all incidents or get a specific incident by ID with advanced filtering by status, severity, type, dates, and more”Search incidents with status status, severity severity, created between start date and end date, and return structured data with id, title, status, severity, and created at”
Create IncidentCreate new incidents with support for different modes and Slack integration”Create a new incident titled incident title with severity severity and type incident type, include summary impact summary, and return structured data with id, title, status, and severity”
Edit IncidentUpdate existing incidents including status, severity, and notification settings”Using incident id, update status to new status and severity to new severity, and return structured data with id, status, and severity”
List AlertsList all alerts with filtering by status, deduplication key, and creation date”List alerts with status alert status created between start date and end date, and return structured data with id, status, deduplication key, and created at”
List Incident AlertsList connections between incidents and alerts with filtering options”Using incident id, list linked alerts and return structured data with incident id, alert id, and alert status”

​
How to Use

1

Create Your Incident.io MCP Node

Go to your node library, search for Incident.io, and click “Create a node with AI”
2

Add Your Prompt

Drag the Incident.io MCP node to your canvas and add your prompt in the text box.
3

Test Your Node

Run the node to see the results. If it works as expected, you’re all set! If you run into issues, check the troubleshooting tips below.
4

Save and Reuse

Once your Incident.io MCP node is working, save it to your library. You can now use this customized node in any workflow.

​
Example Prompts

Here are some prompts that work well with Incident.io MCP: Find Incidents 
Search incidents with status `status` and severity `severity` created between `start date` and `end date`, and return id, title, status, severity, and created at as structured data
Create Incident 
Create a new incident titled `incident title` with severity `severity` and type `incident type`, include impact summary `impact summary`, and return id, title, status, and severity as structured data
Update Incident 
Using `incident id`, set status to `new status` and severity to `new severity`, then return id, status, and severity as structured data
List Alerts 
List alerts with status `alert status` and deduplication key `dedup key` created since `start date`, and return id, status, deduplication key, and created at as structured data
Find Incident-Alert Links 
Using `incident id`, list connected alerts and return incident id, alert id, and alert status as structured data
Find Users 
Find users matching `search term` and return id, name, and email as structured data
Start with focused, single-action prompts and specify the exact output fields you need. MCP nodes return structured data, making it easy to route fields into Google Sheets Writer, Gmail Sender, or other nodes in your workflow.

​
Troubleshooting

If your Incident.io MCP node isn’t working as expected, try these best practices:

​
Keep Prompts Simple and Specific

  • Good: “Search for incident title and return id and status”
  • Bad: “Create an incident for incident title, assign it to assignee email, and list all related alerts”
While the bad prompt might run, it is more efficient to break it into separate nodes. Incident.io MCP works best with focused, single-action prompts.

​
Match What Incident.io Can Do

  • Good: “List alerts with status alert status and return id and status”
  • Bad: “List alerts and send a Slack message to the owner of each alert”
Incident.io MCP focuses on incident and alert data. For Slack announcements, combine it with the Slack Message Sender node in your workflow.

​
Break Complex Tasks Into Steps

Instead of trying to do everything in one prompt (which might cause timeouts and errors): 
Search for all incidents created since `start date` with severity `severity`, find linked alerts, update each incident status to `new status`, and announce in Slack channel `channel name`
Break this into smaller, focused nodes that each handle one task:
1

Step 1: Get Incidents

Search incidents created since start date with severity severity and return incident ids and titles
2

Step 2: Get Alerts

Using incident ids, list connected alerts and return incident id and alert ids
3

Step 3: Update Incidents

Using incident ids, update status to new status and return id and status
In your workflow, connect these nodes sequentially. The incident ids output from Step 1 becomes the input for Step 2, and the incident ids from Step 2 feed into Step 3.

​
Focus on Data Retrieval

Incident.io MCP excels at getting information from Incident.io. For analysis or content creation, connect it to other nodes. Example:
  • Good prompt: “List incidents with status status and return id, title, and severity”
  • Bad prompt: “List incidents with status status, summarize them, and draft a remediation plan”
Use Ask AI to summarize or generate content based on the structured data returned by Incident.io. Keep the Incident.io MCP node focused on retrieval of data from the platform.

​
Troubleshooting Node Creation

If you’re seeing empty outputs in the node creation window (or if you’ve already created or saved the node, hover over it and click “Edit”), use the chat interface to prompt the AI to add debug logs and verify the API response. Specifically mention that you received empty outputs.
In the node creation window (or if you’ve already created or saved the node, hover over it and click “Edit”), use the chat interface to describe in detail what you expected versus what you received.
First click “Fix with Gummie”. If multiple attempts fail, simplify your prompt or contact support.
MCP node creation often requires a few tweaks. Use the chat interface in the node creation window to refine filters, output fields, or pagination. The AI will adjust the node based on your feedback.

​
Need More Help?