incident.io MCP Server
Connect to the incident.io MCP server to create and edit incidents, list alerts, correlate alerts to incidents, and look up responders using AI agents on Gumloop, Claude, or Cursor.
Try incident.io now
Type what you want done. Sign in and run it live with an AI agent.
|
incident.io
Installation
Get StartedCreate a Gumloop Account
To use this MCP, you need a Gumloop account. If you don't have one yet, you can create one for free.
Copy Your Server URL
Copy your MCP server URL and add it to your client. You'll be prompted to authorize on first use.
Tools (6)
List Users
List users in your Incident.io account OR get a specific user by ID. When user_id is provided, returns that single user. Otherwise, lists users with filtering options and automatic pagination support.
List Incidents
List incidents in your organization OR get a specific incident by ID. When incident_id is provided, returns that single incident. Otherwise, lists incidents with advanced filtering options and automatic pagination support.
Create Incident
Create a new incident in your organization. Note: retrospective mode incidents are not announced in Slack.
Edit Incident
Edit an existing incident's properties like severity, status, custom fields, and role assignments
List Alerts
List all alerts for your account with filtering options
List Incident Alerts
List connections/relationships between incidents and alerts
What is incident.io MCP?
The incident.io MCP server gives AI agents access to your incident.io workspace. That means agents can create new incidents, edit an incident’s severity, status, name, summary, and call URL, list and filter incidents by status category, severity, type, and date range, list monitoring alerts, trace which alerts are linked to which incidents, and look up users by email or Slack ID. It also exposes your configured severities and incident roles as read-only resources, so an agent always has the right context when it triages.
If your on-call engineers spend their first minutes of an incident clicking through the dashboard to declare it, set a severity, and figure out who is responding, an AI agent can take over a lot of that opening busywork. Describe what you need, and your AI agent will handle the incident declaration and triage for you.
MCP stands for Model Context Protocol. It’s an open standard that gives AI agents a way to connect to external tools and services. Instead of writing code against the incident.io REST API, handling Bearer authentication, pagination, and rate limits, and resolving INC-123 references to internal IDs yourself, you add your incident.io API key to Gumloop once. After that, you can run incident triage just by chatting with your AI agent.
Related MCP servers
PagerDuty MCP Server
Interact with PagerDuty incident management and on-call scheduling
Datadog MCP Server
Interact with Datadog to monitor infrastructure, query metrics, search logs, and manage incidents
Slack MCP Server
Interact with Slack channels and messages
JIRA MCP Server
Interact with JIRA for project management, issue tracking, and user information access.
Linear MCP Server
Interact with Linear issue tracking and project management
Github MCP Server
Server for interacting with Github
What you can do with incident.io MCP on Gumloop
Create incidents on demand
Declare a new incident with a name, visibility, and severity, plus an optional summary, type, and starting status. You can target a specific Slack workspace and override the incident channel name so response coordination starts in the right place. A built-in deduplication key keeps an agent from creating the same incident twice on a retry.
Edit severity, status, and incident details
Update an existing incident’s severity, status, name, summary, call URL, or Slack channel name as the situation changes. Your AI agent can promote a minor incident to critical, move it from triage to live, or attach a video call link, then control whether the incident channel gets notified.
List and filter incidents
Pull incidents with rich filtering by status category (triage, live, learning, closed, and more), severity, incident type, mode, and created or updated date ranges. You can also fetch a single incident directly, and the server resolves human-readable INC-123 references to the full record for you.
List alerts from your monitoring stack
List alerts with filtering by status, deduplication key, and date ranges. An AI agent can scan for firing alerts, group them by deduplication key, and surface the noisy ones that deserve a closer look.
Correlate alerts to incidents
List the connections between incidents and alerts to see exactly which monitoring alerts triggered which incidents. This gives an agent the raw material for root-cause analysis and post-incident reviews.
Look up users and responders
Find users by ID, email, or Slack user ID so an agent has the responder context it needs. Useful for matching an alert or incident to the right person without leaving the conversation.
Read your severity and role configuration
Browse your organization’s configured severity levels and incident roles as read-only MCP resources. An agent can reference the correct severity ID when it creates or edits an incident, so it stays aligned with how your team already classifies incidents.
How to connect the Gumloop incident.io MCP Server
- 1
Create a free Gumloop account
Sign up at gumloop.com. No credit card required.
- 2
Add the incident.io MCP server
Copy your MCP server URL from Gumloop and add it to your preferred client (Claude, Cursor, or Gumloop workflows). You'll authorize on first use.
- 3
Start using incident.io in your AI workflows
That's it. Your AI agent can now create and edit incidents, filter the incident list, list and correlate alerts, and look up responders across your incident.io workspace. Use it inside a Gumloop automation, in Claude Desktop, or in Cursor.
incident.io MCP use cases
Chat-driven incident declaration for on-call engineers
When something breaks, an engineer can describe the problem in chat and a Gumloop agent reads the configured severities, picks the right one, creates the incident with the correct Slack channel, and posts the new INC reference back to the team. The first responder skips the dashboard and gets straight to fixing.
Alert triage and noise reduction for SRE teams
An AI agent can list firing alerts, group them by deduplication key, and check which ones are already linked to an open incident using the incident-to-alert connections. It then flags only the unhandled, high-signal alerts in Slack, so the team catches real problems without wading through a noisy alert feed.
Severity escalation for incident commanders
As an incident grows, a commander can tell an agent to bump the severity and move the status from triage to live. The agent edits the incident, updates the call URL, and notifies the incident channel, keeping the record accurate while the humans stay focused on the response.
Post-incident review prep for engineering leaders
After an incident closes, an agent can pull the incident details, list every alert correlated to it, and look up the responders involved, then compile a clean review packet into Google Docs or a Slack message. Engineering leaders walk into the retrospective with the timeline of alerts and the cast of responders already assembled.
Weekly incident reporting for DevOps managers
Pull every incident from the past week filtered by status category and severity, summarize how many were critical, how long they stayed live, and which alerts drove them, then drop the rollup into Google Sheets or a Slack channel. Managers get a current reliability snapshot without anyone exporting data by hand.
Why use Gumloop for incident.io MCP
Add your incident.io API key once, stored securely
Most incident.io MCP servers you’ll find on GitHub require you to store your API key in environment variables and write code to handle Bearer authentication, pagination, and rate limits. With Gumloop you add your incident.io API key once and it’s stored securely. No env vars, token management, or coding against the incident.io API necessary.
Works with multiple MCP clients
Use the incident.io MCP server endpoint in Claude Desktop, Cursor, or directly inside Gumloop agents. Same server URL, works with any MCP client.
Chain incident.io with 100+ other integrations
Combine incident.io with Slack, Gmail, Google Sheets, Google Docs, and other MCP tools in a single AI agent. An agent can read a firing alert, create an incident in incident.io, post the INC reference to Slack, and log the details to a sheet, all in one run.
Enterprise-grade and scalable
Built for teams, with role-based permissions and dedicated support for Pro users. Whether you run a single on-call rotation or a large reliability org, the incident.io MCP server scales with you. For details on Gumloop’s security practices, see trust.gumloop.com.
Pricing includes a free plan
You can test the incident.io MCP integration on Gumloop’s free tier before committing. Paid plans start at $37/month.
Frequently asked questions
Ship incident.io agents in minutes
Connect any AI agent to 100+ MCP servers, fully hosted, zero setup.