MCP / Developer tools

incident.io MCP: developer workflows

Incident management and response platform. Connect it to Claude, Codex, Cursor or any MCP client through one FlyMy.AI MCP.

Connect incident.io What it can do

Your own API key112 actionsDeveloper tools

$ YOUR NEXT RUN

Claude CodeCodexCursor

Any agent

Use incident.io MCP in your assistant

Paste this prompt into Claude Code, Codex, Cursor or any agent. It reads the guide and helps you connect.

Read https://flymy.ai/skill.md and https://flymy.ai/mcp/incident-io.md. Help me connect incident.io MCP to this assistant. Then help me run this task: Use incident.io to create alert attributes v2. Ask me for the required inputs first and show the result.

Open FlyMy.AI Download brief

What incident.io MCP can do

112 actions in the FlyMy.AI catalog, the most used first. Your agent finds them through search_tools and calls the one the task needs.

Action	What it does
# `INCIDENT_IO_CREATE_ALERT_ATTRIBUTES_V2`	Create an alert attribute in incident.io.
# `INCIDENT_IO_CREATE_ALERT_ROUTES_V2`	Create an alert route in incident.io.
# `INCIDENT_IO_CREATE_ALERT_SOURCES_V2`	Create a new alert source in incident.io.
# `INCIDENT_IO_CREATE_CATALOG_ENTRIES_V2`	Create a catalog entry in incident.io.
# `INCIDENT_IO_CREATE_CATALOG_ENTRIES_V3`	Create a catalog entry in incident.io using the V3 API.
# `INCIDENT_IO_CREATE_CATALOG_TYPES_V3`	Create a new catalog type in incident.io V3 API.
# `INCIDENT_IO_CREATE_CUSTOM_FIELDS_V2`	Create a custom field in incident.io using the V2 API.
# `INCIDENT_IO_CREATE_CUSTOM_FIELD_OPTIONS_V1`	Create a new custom field option in incident.io.
# `INCIDENT_IO_CREATE_ESCALATIONS_V2`	Create an escalation in incident.io.
# `INCIDENT_IO_CREATE_INCIDENTS_V1`	Create a new incident in incident.io.
# `INCIDENT_IO_CREATE_INCIDENTS_V2`	Create a new incident in incident.io using the V2 API.
# `INCIDENT_IO_CREATE_INCIDENT_ROLES_V1`	Create a new incident role in incident.io.

Show all 112 actions

Action	What it does
# `INCIDENT_IO_CREATE_INCIDENT_ROLES_V2`	Create a new incident role in incident.io using the V2 API.
# `INCIDENT_IO_CREATE_INCIDENT_STATUS`	Create a new incident status in incident.io.
# `INCIDENT_IO_CREATE_MANAGED_RESOURCES_V2`	Create a managed resource in incident.io.
# `INCIDENT_IO_CREATE_SEVERITIES_V1`	Create a new severity level in incident.io.
# `INCIDENT_IO_DELETE_ALERT_ATTRIBUTES_V2`	Delete an alert attribute from incident.io.
# `INCIDENT_IO_DELETE_ALERT_ROUTES_V2`	Delete an alert route from incident.io.
# `INCIDENT_IO_DELETE_ALERT_SOURCES_V2`	Delete an alert source from incident.io.
# `INCIDENT_IO_DELETE_CATALOG_ENTRIES_V2`	Delete a catalog entry from incident.io.
# `INCIDENT_IO_DELETE_CATALOG_ENTRIES_V3`	Archive a catalog entry from incident.io using V3 API.
# `INCIDENT_IO_DELETE_CATALOG_TYPES_V2`	Delete a catalog type from incident.io.
# `INCIDENT_IO_DELETE_CATALOG_TYPES_V3`	Archive a catalog type and all its entries from incident.io.
# `INCIDENT_IO_DELETE_CUSTOM_FIELD`	Delete a custom field from incident.io.
# `INCIDENT_IO_DELETE_CUSTOM_FIELDS_V2`	Delete a custom field from incident.io using the V2 API.
# `INCIDENT_IO_DELETE_CUSTOM_FIELD_OPTIONS_V1`	Delete a custom field option in incident.io.
# `INCIDENT_IO_DELETE_ESCALATION_PATHS_V2`	Delete an escalation path from incident.io.
# `INCIDENT_IO_DELETE_INCIDENT_ROLES_V2`	Delete an incident role by ID.
# `INCIDENT_IO_DELETE_INCIDENT_ROLE_V1`	Delete an incident role by ID.
# `INCIDENT_IO_DELETE_INCIDENT_STATUS_V1`	Delete an incident status by its ID.
# `INCIDENT_IO_DELETE_SCHEDULES_V2`	Delete a schedule from incident.io.
# `INCIDENT_IO_DELETE_SEVERITY`	Delete a severity in incident.io.
# `INCIDENT_IO_DELETE_WORKFLOWS_V2`	Delete a workflow from incident.io using the V2 API.
# `INCIDENT_IO_EDIT_INCIDENTS_V2`	Edit an existing incident in incident.io.
# `INCIDENT_IO_GET_ALERT_ATTRIBUTES_V2`	Retrieve a specific alert attribute by its ID from incident.io.
# `INCIDENT_IO_GET_ALERT_ROUTES_V2`	Retrieve a specific alert route configuration by its ID from incident.io.
# `INCIDENT_IO_GET_ALERT_SOURCES_V2`	Retrieve a specific alert source by its ID from incident.io.
# `INCIDENT_IO_GET_CATALOG_ENTRIES_V2`	Retrieve a specific catalog entry by ID from incident.io.
# `INCIDENT_IO_GET_CATALOG_ENTRY_V3`	Retrieve a specific catalog entry by ID from incident.io.
# `INCIDENT_IO_GET_CATALOG_TYPES_V2`	Retrieve a specific catalog type by ID from incident.io.
# `INCIDENT_IO_GET_CATALOG_TYPES_V3`	Retrieve a specific catalog type by ID from incident.io V3 API.
# `INCIDENT_IO_GET_CUSTOM_FIELD_OPTIONS_V1`	Retrieve a specific custom field option by its ID.
# `INCIDENT_IO_GET_CUSTOM_FIELD_V1`	Retrieve details of a specific custom field by ID in incident.io.
# `INCIDENT_IO_GET_CUSTOM_FIELD_V2`	Retrieve details of a specific custom field by ID using the V2 API in incident.io.
# `INCIDENT_IO_GET_ESCALATIONS_V2`	Retrieve a specific escalation by ID from incident.io.
# `INCIDENT_IO_GET_INCIDENT_ROLES_V1`	Retrieve a specific incident role by ID.
# `INCIDENT_IO_GET_INCIDENT_ROLES_V2`	Retrieve a specific incident role by ID using V2 API.
# `INCIDENT_IO_GET_INCIDENT_STATUS`	Retrieve details of a specific incident status by ID.
# `INCIDENT_IO_GET_INCIDENT_TIMESTAMPS_V2`	Retrieve a specific incident timestamp by ID using V2 API.
# `INCIDENT_IO_GET_INCIDENT_TYPE`	Retrieve detailed information about a specific incident type by ID.
# `INCIDENT_IO_GET_INCIDENT_V1`	Retrieve a specific incident by ID.
# `INCIDENT_IO_GET_INCIDENT_V2`	Retrieve a specific incident by ID using V2 API.
# `INCIDENT_IO_GET_SCHEDULES_V2`	Retrieve a specific schedule by ID from incident.io using V2 API.
# `INCIDENT_IO_GET_SEVERITIES_V1`	Retrieve a specific severity by ID from incident.io.
# `INCIDENT_IO_GET_USERS_V2`	Retrieve a specific user by ID from incident.io using V2 API.
# `INCIDENT_IO_GET_WORKFLOWS_V2`	Retrieve a specific workflow by ID from incident.io.
# `INCIDENT_IO_LIST_ACTIONS_V1`	List actions from incidents.
# `INCIDENT_IO_LIST_ACTIONS_V2`	Retrieve a list of actions from incident.io.
# `INCIDENT_IO_LIST_ALERTS_V2`	List alerts from incident.io.
# `INCIDENT_IO_LIST_ALERT_ATTRIBUTES_V2`	List all available alert attributes.
# `INCIDENT_IO_LIST_ALERT_ROUTES_V2`	List alert routes from incident.io.
# `INCIDENT_IO_LIST_ALERT_SOURCES_V2`	List all configured alert sources in incident.io.
# `INCIDENT_IO_LIST_CATALOG_ENTRIES_V2`	List entries from a catalog type in incident.io.
# `INCIDENT_IO_LIST_CATALOG_ENTRIES_V3`	List entries from a catalog type in incident.io.
# `INCIDENT_IO_LIST_CATALOG_RESOURCES_V2`	Retrieve all available catalog resource types.
# `INCIDENT_IO_LIST_CATALOG_RESOURCES_V3`	Retrieve all available catalog resource types from the V3 API.
# `INCIDENT_IO_LIST_CATALOG_TYPES_V2`	Retrieve all catalog types configured for an organization.
# `INCIDENT_IO_LIST_CATALOG_TYPES_V3`	Retrieve all catalog types configured for an organization using V3 API.
# `INCIDENT_IO_LIST_CUSTOM_FIELDS_V1`	List all custom fields for an organization.
# `INCIDENT_IO_LIST_CUSTOM_FIELDS_V2`	List all custom fields V2 for an organization.
# `INCIDENT_IO_LIST_CUSTOM_FIELD_OPTIONS_V1`	List all options for a specific custom field in incident.io.
# `INCIDENT_IO_LIST_ESCALATIONS_V2`	List escalations from incident.io.
# `INCIDENT_IO_LIST_ESCALATION_PATHS_V2`	List escalation paths from incident.io.
# `INCIDENT_IO_LIST_FOLLOW_UPS_V2`	Retrieve a list of follow-ups from incident.io.
# `INCIDENT_IO_LIST_IDENTITY_V1`	Retrieve identity information for the current API key.
# `INCIDENT_IO_LIST_INCIDENTS_V1`	List incidents from incident.io.
# `INCIDENT_IO_LIST_INCIDENTS_V2`	List incidents from incident.io using the V2 API.
# `INCIDENT_IO_LIST_INCIDENT_ALERTS_V2`	List incident alerts from incident.io.
# `INCIDENT_IO_LIST_INCIDENT_ATTACHMENTS_V1`	List incident attachments from incident.io.
# `INCIDENT_IO_LIST_INCIDENT_RELATIONSHIPS_V1`	List incident relationships for a given incident.
# `INCIDENT_IO_LIST_INCIDENT_ROLES_V1`	List all incident roles for an organization.
# `INCIDENT_IO_LIST_INCIDENT_ROLES_V2`	List all incident roles for an organization using V2 API.
# `INCIDENT_IO_LIST_INCIDENT_STATUSES_V1`	List all incident statuses configured for an organization.
# `INCIDENT_IO_LIST_INCIDENT_TIMESTAMPS_V2`	List all incident timestamp configurations using V2 API.
# `INCIDENT_IO_LIST_INCIDENT_TYPES_V1`	List all incident types for an organization.
# `INCIDENT_IO_LIST_INCIDENT_UPDATES_V2`	List incident updates from incident.io.
# `INCIDENT_IO_LIST_IP_ALLOWLISTS`	Retrieve the current IP allowlist configuration for incident.io.
# `INCIDENT_IO_LIST_SCHEDULES_V2`	List schedules from incident.io.
# `INCIDENT_IO_LIST_SCHEDULE_ENTRIES_V2`	List schedule entries for a specific schedule in incident.io.
# `INCIDENT_IO_LIST_SEVERITIES_V1`	Retrieve all incident severities configured for an organization.
# `INCIDENT_IO_LIST_STATUS_PAGES_V2`	List status pages from incident.io.
# `INCIDENT_IO_LIST_USERS_V2`	List users in incident.io.
# `INCIDENT_IO_LIST_WORKFLOWS_V2`	List workflows from incident.io.
# `INCIDENT_IO_UPDATE_ALERT_ATTRIBUTES_V2`	Update an alert attribute in incident.io.
# `INCIDENT_IO_UPDATE_ALERT_SOURCES_V2`	Update an existing alert source configuration in incident.io.
# `INCIDENT_IO_UPDATE_CATALOG_ENTRIES_BULK_V3`	Bulk update catalog entries in incident.io v3 API.
# `INCIDENT_IO_UPDATE_CATALOG_ENTRIES_V2`	Update an existing catalog entry in incident.io.
# `INCIDENT_IO_UPDATE_CATALOG_ENTRIES_V3`	Update an existing catalog entry in incident.io using the v3 API.
# `INCIDENT_IO_UPDATE_CATALOG_TYPES_V2`	Update a catalog type in incident.io.
# `INCIDENT_IO_UPDATE_CATALOG_TYPES_V3`	Update a catalog type in incident.io V3 API.
# `INCIDENT_IO_UPDATE_CUSTOM_FIELDS_V1`	Update an existing custom field configuration in incident.io.
# `INCIDENT_IO_UPDATE_CUSTOM_FIELDS_V2`	Update an existing custom field in incident.io using the V2 API.
# `INCIDENT_IO_UPDATE_CUSTOM_FIELD_OPTION_V1`	Update a custom field option in incident.io.
# `INCIDENT_IO_UPDATE_ESCALATION_PATHS_V2`	Update an escalation path in incident.io.
# `INCIDENT_IO_UPDATE_INCIDENT_ROLE`	Update an existing incident role in incident.io.
# `INCIDENT_IO_UPDATE_INCIDENT_ROLES_V2`	Update an existing incident role in incident.io using the V2 API.
# `INCIDENT_IO_UPDATE_INCIDENT_STATUS`	Update an existing incident status in incident.io.
# `INCIDENT_IO_UPDATE_SCHEDULES_V2`	Update an existing schedule in incident.io.
# `INCIDENT_IO_UPDATE_SCHEMA_CATALOG_TYPES_V2`	Update the schema of a catalog type in incident.io.
# `INCIDENT_IO_UPDATE_SCHEMA_CATALOG_TYPES_V3`	Update the schema of a catalog type in incident.io V3 API.
# `INCIDENT_IO_UPDATE_SEVERITIES_V1`	Update a severity in incident.io.
# `INCIDENT_IO_UPDATE_WORKFLOWS_V2`	Update an existing workflow in incident.io using the V2 API.

Ask your agent

Requests to paste as they are. Each one runs on the actions named under it.

“Use incident.io to create alert attributes v2. Ask me for the required inputs first and show the result.”uses INCIDENT_IO_CREATE_ALERT_ATTRIBUTES_V2

“Use incident.io to create alert routes v2. Ask me for the required inputs first and show the result.”uses INCIDENT_IO_CREATE_ALERT_ROUTES_V2

“Use incident.io to create alert sources v2. Ask me for the required inputs first and show the result.”uses INCIDENT_IO_CREATE_ALERT_SOURCES_V2

Connect incident.io in a minute

One MCP for every integration. Add it once, then every MCP in the catalog is a request away.

01
Add FlyMy.AI
Add the FlyMy.AI MCP to your assistant with one of the commands below and sign in. No key to copy.
02
Add your API Key
Paste it into the incident.io connection settings once; it stays with FlyMy.AI, never in a prompt or a chat.
- API Key - Generate at https://app.incident.io/settings/api-keys Get API key →
03
Ask
Paste a request from this page. Every run shows what it cost.

Claude Code

claude mcp add --transport http flymyai https://mcp-agents.flymy.ai/mcp

Then run /mcp in Claude Code and sign in.

Codex

codex mcp add flymy --url https://mcp-agents.flymy.ai/mcp

Then run codex mcp login flymy to sign in.

claude.ai and Claude Desktop

https://mcp-agents.flymy.ai/mcp

Settings, Connectors, Add custom connector: paste this URL.

Pay per run

FlyMy.AI bills the run: the model and the tool's seconds. Calls go to your own incident.io account, under its plan and limits. No seats and no minimum.

See usage pricing →

Go to the source

incident.io in the docs →incident.io connection settings →incident.io website →Every MCP in the catalog →Usage pricing →

From the FlyMy.AI platform catalog of 2026-11-03: name, description, actions and setup as the platform lists them. Examples are requests to paste, not recorded runs.

incident.io MCP: developer workflows

Use incident.io MCP in your assistant

What incident.io MCP can do

Ask your agent

Connect incident.io in a minute

Add FlyMy.AI

Add your API Key

Ask

Pay per run

More Developer tools MCPs

1Password

Ably

Abstract

AbuseIPDB

Addressfinder

Addresszen

Go to the source