Skip to content
Weavz
Menu
incident.io

incident.io MCP integration

Incident response, on-call, alerts, follow-ups, and status workflows.

Sign in, add incident.io in Apps, then choose the account your AI can use.

15 tools
4 triggers
Use withChatGPTClaudeClaude CodeCursorCodexMCP clientsSetup guide

Tools

Name
validate_connection

Validate the incident.io API key by reading incident severity configuration.

list_incidents

List incidents with current incident.io V2 filters and cursor pagination.

search_incidents

Find incidents by common operational filters such as status category, severity, type, mode, and date range.

get_incident

Get a single incident by full incident ID or numeric reference.

list_severities

List incident severity IDs for the organization.

list_incident_statuses

List incident status IDs and categories for the organization.

list_incident_types

List incident type IDs for the organization.

list_users

List incident.io users, optionally filtered by email or Slack user ID.

create_incident

Create a new incident using incident.io Incidents V2. The API key must have create incident permission.

edit_incident

Edit selected properties of an existing incident. Omitted fields are ignored by incident.io.

list_incident_updates

List incident updates for the organization or a specific incident.

list_actions

List incident.io action items, optionally for a specific incident.

get_action

Get a single incident.io action item.

list_follow_ups

List incident follow-ups, optionally filtered by incident, mode, or assignee team.

get_follow_up

Get a single incident follow-up.

Triggers

Name
webhook_event_received

Receive any incident.io webhook payload from a manually configured webhook endpoint.

incident_created

Receive public or private incident created webhook events.

incident_updated

Receive public or private incident updated webhook events.

incident_status_updated

Receive public incident status updated webhook events.

Quick Start

TypeScript
import { WeavzClient } from '@weavz-io/sdk'

const weavz = new WeavzClient({ apiKey: 'wvz_...' })

const result = await weavz.actions.execute('incident-io', 'validate_connection', {
  workspaceId: '550e8400-e29b-41d4-a716-446655440000',
  integrationAlias: 'incident-io',
  input: { /* ... */ },
})

Related Integrations

Works well with

Frequently Asked Questions

Is there a incident.io MCP server through Weavz?

Yes. Add the incident.io integration to a Weavz workspace, enable the actions you need and connect any required account. Weavz provides the workspace MCP endpoint in Tool Mode or Code Mode. The catalog currently lists 15 incident.io actions.

What can an AI agent do with incident.io?

Available actions include Validate Connection, List Incidents, Search Incidents, Get Incident, List Severities, and more. Your workspace exposes only the actions you enable. The agent also needs the intended account access and any required input values.

How do I connect incident.io to Claude or ChatGPT?

Use a compatible remote MCP client, add the Weavz connector and choose a workspace. Add incident.io, connect the required account and review the enabled actions. Client availability and account requirements vary; adding the connector does not authorize every app automatically.

Can I use incident.io through an API or SDK?

Yes, supported actions can run through the Weavz REST API, TypeScript SDK or Python SDK. Configure a workspace and the required connections, use scoped access, and pass the intended end-user context when acting for a customer.

What authentication does incident.io require?

The catalog lists custom credentials for incident.io. Use Hosted Connect to authorize the intended account. Required permissions, provider app access and available connection methods depend on the integration.

How do I review sensitive incident.io actions?

Limit enabled actions, scope credentials to the intended user and configure Human Gates for the operations that need review. A matching policy can pause a send, record change or other sensitive action for an approver before execution.

What limits or costs apply to incident.io?

Weavz plan limits apply to the actions and resources you use. The external provider may also require an account, a paid plan, API credits or specific permissions, and may enforce its own rate limits. Check current Weavz pricing and the provider’s terms before rollout.

What incident.io triggers are available?

The catalog lists 4 triggers, including Webhook Event Received, Incident Created, Incident Updated, Incident Status Updated. Configure the trigger and your event handler before using incoming events to start work.

Connect incident.io in minutes

Get 20,000 free action executions every month. No credit card required.