What is incident.io MCP?

It's an MCP (Model Context Protocol) server that connects incident.io to your AI, giving the agent tools to act on your data — through a single remote link.

Which AI clients does it work with?

Any MCP-compatible client: Claude (web, desktop and mobile), Cursor, ChatGPT with connectors, OpenClaw and other agents.

No. Paste the remote URL into your client, authenticate once, and you're done — no packages to install, no code to write.

Is it secure? Can the AI change my data?

Access is authorized by you and can be revoked anytime. Permissions follow what incident.io exposes; you approve them when connecting.

How much does it cost?

You start free and upgrade when you need more usage. Billing and limits are managed in your mcp.ai account.

Can I cancel anytime?

Yes. Plans are monthly and can be cancelled at any time, with no lock-in.

incident.io MCP Server and REST API

mcp.ai

incident.io

Conecta tu cuenta incident.io y usa 86 herramientas de herramientas de desarrollo directamente desde tu agente de IA. Conecta con tu propia clave de API.

Instala en tu cliente

URL del servidor MCP

https://api.mcp.ai/p_incident_io

Conexión segura vía OAuth 2.0

Herramientas (86)

Para desarrolladores

Docs de API y agente

Docs legibles por máquina para conectar este servidor a un agente o llamarlo por REST.

Skill (cómo usar)

Markdown: usar vía MCP o vía API REST directa.

Abrir

llms.txt

Especificación de este servidor legible por agentes.

Abrir

Para agentes

Prompt de instalación — pégalo en Claude, ChatGPT, Cursor o cualquier agente MCP y se conecta solo.

Abrir

Colección Postman

Importa la API REST en Postman.

Descargar

Preguntas

Preguntas frecuentes

En la práctica

Ejemplos de prompts

Cosas reales que puedes pedirle a tu agente con este servidor activado.

¿Qué puedo hacer en incident.io?

Muéstrame un resumen de mi cuenta de incident.io

Etiquetas relacionadas

developer tools

incident.io

Herramientas (86)

incident_io_create_alert_attributes_v2Tool to create an alert attribute in incident.io. Use when you need to define structured data fields that can be parsed from alerts coming in via alert sources. Alert attributes allow you to extract a

incident_io_create_alert_routes_v2Tool to create an alert route in incident.io. Use when you need to configure how alerts should be processed, routed, and potentially converted into incidents based on conditions, grouping rules, and t

incident_io_create_alert_sources_v2Tool to create a new alert source in incident.io. Use when you need to set up a new integration for receiving alerts from external systems via HTTP webhooks or manual entry.

incident_io_create_catalog_entries_v3Tool to create a catalog entry in incident.io using the V3 API. Use when you need to add a new entry to a catalog type with specific attribute values. Catalog entries represent items like teams, servi

incident_io_create_catalog_types_v3Tool to create a new catalog type in incident.io V3 API. Use when you need to define custom resource types for your organization's catalog, such as teams, services, or infrastructure components.

incident_io_create_custom_field_options_v1Tool to create a new custom field option in incident.io. Use when you need to add a new selectable value to an existing custom field.

incident_io_create_custom_fields_v2Tool to create a custom field in incident.io using the V2 API. Use when you need to add a new custom field to track additional information during incidents.

incident_io_create_escalations_v2Tool to create an escalation in incident.io. Use when you need to page users to respond to alerts. You must specify either an escalation_path_id or direct targets (users/schedules).

incident_io_create_incident_roles_v2Tool to create a new incident role in incident.io using the V2 API. Use when you need to define a new role type that can be assigned during incidents to organize responsibilities and ensure the right

incident_io_create_incident_statusTool to create a new incident status in incident.io. Use when you need to add a custom status for categorizing incidents as 'live' (active), 'learning' (post-incident), or 'closed'.

incident_io_create_incidents_v2Tool to create a new incident in incident.io using the V2 API. Use when you need to report and track an operational issue or outage. Requires at minimum an idempotency_key and visibility setting. Opti

incident_io_create_managed_resources_v2Tool to create a managed resource in incident.io. Use when you need to mark a resource (schedule, escalation path, or workflow) as being managed by an external system like Terraform or a custom automa

incident_io_create_severities_v1Tool to create a new severity level in incident.io. Use when you need to define a new severity classification for incidents with a specific rank and description.

incident_io_delete_alert_attributes_v2Tool to delete an alert attribute from incident.io. Use when you need to remove an alert attribute that is no longer needed or was created in error.

incident_io_delete_alert_routes_v2Tool to delete an alert route from incident.io. Use when you need to remove an alert route configuration that is no longer needed or was created in error.

incident_io_delete_alert_sources_v2Tool to delete an alert source from incident.io. Use when you need to remove an alert source that is no longer needed or was created in error.

incident_io_delete_catalog_entries_v3Tool to archive a catalog entry from incident.io using V3 API. Use when you need to remove a catalog entry that is no longer needed. This operation archives the entry from the catalog.

incident_io_delete_catalog_types_v3Tool to archive a catalog type and all its entries from incident.io. Use when you need to remove a catalog type that is no longer needed.

incident_io_delete_custom_fieldTool to delete a custom field from incident.io. Use when you need to remove a custom field definition. The deletion is permanent and cannot be undone.

incident_io_delete_custom_field_options_v1Tool to delete a custom field option in incident.io. Use when you need to permanently remove a custom field option by its ID.

incident_io_delete_custom_fields_v2Tool to delete a custom field from incident.io using the V2 API. Use when you need to permanently remove a custom field definition by its ID.

incident_io_delete_escalation_paths_v2Tool to delete an escalation path from incident.io. Use when you need to remove an escalation path that is no longer needed or was created in error.

incident_io_delete_incident_roles_v2Tool to delete an incident role by ID. Use when you need to permanently remove an incident role from incident.io.

incident_io_delete_incident_status_v1Tool to delete an incident status by its ID. Use when you need to remove an incident status from the system.

incident_io_delete_schedules_v2Tool to delete a schedule from incident.io. Use when you need to remove a schedule that is no longer needed or was created in error.

incident_io_delete_severityTool to delete a severity in incident.io. Use when you need to permanently remove a severity level from your incident management configuration.

incident_io_delete_workflows_v2Tool to delete a workflow from incident.io using the V2 API. Use when you need to permanently remove a workflow definition by its ID.

incident_io_edit_incidents_v2Tool to edit an existing incident in incident.io. Use when you need to update incident details like name, summary, severity, status, custom fields, or role assignments.

incident_io_get_alert_attributes_v2Tool to retrieve a specific alert attribute by its ID from incident.io. Use when you need to get details about an alert attribute such as its type, whether it's required, or if it accepts arrays.

incident_io_get_alert_routes_v2Tool to retrieve a specific alert route configuration by its ID from incident.io. Use when you need to view the details of an alert route, including its conditions, escalation bindings, and incident t

incident_io_get_alert_sources_v2Tool to retrieve a specific alert source by its ID from incident.io. Use when you need to get details about an alert source configuration including its template and HTTP options.

incident_io_get_catalog_entry_v3Tool to retrieve a specific catalog entry by ID from incident.io. Use when you need to get details about a catalog entry including its attributes and values.

incident_io_get_catalog_types_v3Tool to retrieve a specific catalog type by ID from incident.io V3 API. Use when you need to get details about a catalog type's configuration, schema, or metadata.

incident_io_get_custom_field_options_v1Tool to retrieve a specific custom field option by its ID. Use when you need details about a custom field option in incident.io.

incident_io_get_custom_field_v1Tool to retrieve details of a specific custom field by ID in incident.io. Use when you need information about a custom field's configuration, options, or metadata.

incident_io_get_custom_field_v2Tool to retrieve details of a specific custom field by ID using the V2 API in incident.io. Use when you need information about a custom field's configuration or metadata from the V2 endpoint.

incident_io_get_escalations_v2Tool to retrieve a specific escalation by ID from incident.io. Use when you need detailed information about an escalation including its status, priority, creator, events, and related incidents/alerts.

incident_io_get_incident_roles_v2Tool to retrieve a specific incident role by ID using V2 API. Use when you need to get details about a specific incident role.

incident_io_get_incident_statusTool to retrieve details of a specific incident status by ID. Use when you need to get information about a particular incident status configuration.

incident_io_get_incident_timestamps_v2Tool to retrieve a specific incident timestamp by ID using V2 API. Use when you need to get details about a specific incident timestamp configuration.

incident_io_get_incident_typeTool to retrieve detailed information about a specific incident type by ID. Use when you need to view configuration details, settings, or properties of a particular incident type.

incident_io_get_incident_v2Tool to retrieve a specific incident by ID using V2 API. Use when you need detailed information about an incident including duration metrics, timestamps, and workload data.

incident_io_get_schedules_v2Tool to retrieve a specific schedule by ID from incident.io using V2 API. Use when you need to view details about an on-call schedule, including rotations, shifts, and configuration.

incident_io_get_severities_v1Tool to retrieve a specific severity by ID from incident.io. Use when you need to fetch details about a particular severity level.

incident_io_get_users_v2Tool to retrieve a specific user by ID from incident.io using V2 API. Use when you need to get detailed information about a user including their role assignments.

incident_io_get_workflows_v2Tool to retrieve a specific workflow by ID from incident.io. Use when you need to get details about a workflow's configuration, steps, conditions, and triggers.

incident_io_list_actions_v1Tool to list actions from incidents. Use when you need to retrieve actions associated with incidents, filter by follow-up status, or get actions for a specific incident. By default returns actions fro

incident_io_list_actions_v2Tool to retrieve a list of actions from incident.io. Use when you need to view existing actions, optionally filtered by incident ID or incident mode.

incident_io_list_alert_attributes_v2Tool to list all available alert attributes. Use when you need to retrieve the schema of attributes that can be used with alerts.

incident_io_list_alert_routes_v2Tool to list alert routes from incident.io. Use when you need to retrieve configured alert routes with pagination support.

incident_io_list_alert_sources_v2Tool to list all configured alert sources in incident.io. Use when you need to retrieve alert sources that send alerts to incident.io for routing.

incident_io_list_alerts_v2Tool to list alerts from incident.io. Use when you need to retrieve alerts for the organisation with pagination support.

incident_io_list_catalog_entries_v3Tool to list entries from a catalog type in incident.io. Use when you need to retrieve catalog entries for a specific catalog type with pagination and filtering support.

incident_io_list_catalog_resources_v3Tool to retrieve all available catalog resource types from the V3 API. Use when you need to list the types of data that can be held within the catalog or see what attribute types are available for upd

incident_io_list_catalog_types_v3Tool to retrieve all catalog types configured for an organization using V3 API. Use when you need to list available catalog types or understand the catalog schema structure. This includes both synced

incident_io_list_escalation_paths_v2Tool to list escalation paths from incident.io. Use when you need to retrieve configured escalation paths with pagination support.

incident_io_list_escalations_v2Tool to list escalations from incident.io. Use when you need to retrieve escalations for the organisation with pagination support.

incident_io_list_follow_ups_v2Tool to retrieve a list of follow-ups from incident.io. Use when you need to view existing follow-ups, optionally filtered by incident ID or incident mode.

incident_io_list_identity_v1Tool to retrieve identity information for the current API key. Use to check which organization and roles are associated with the API key.

incident_io_list_incident_alerts_v2Tool to list incident alerts from incident.io. Use when you need to retrieve connections between incidents and alerts with optional filtering by incident_id or alert_id.

incident_io_list_incident_attachments_v1Tool to list incident attachments from incident.io. Use when you need to retrieve external resources linked to incidents, such as PagerDuty incidents, Jira issues, or GitHub pull requests. Filter by i

incident_io_list_incident_relationships_v1Tool to list incident relationships for a given incident. Use when you need to retrieve relationships between incidents such as blocking dependencies, causal links, or general associations.

incident_io_list_incident_roles_v2Tool to list all incident roles for an organization using V2 API. Use when you need to retrieve available incident roles and their configurations.

incident_io_list_incident_updates_v2Tool to list incident updates from incident.io. Use when you need to retrieve updates for incidents with optional filtering by incident ID and pagination support.

incident_io_list_incidents_v2Tool to list incidents from incident.io using the V2 API. Use when you need to retrieve incidents with advanced filtering by status, severity, type, timestamps, and pagination support.

incident_io_list_ip_allowlistsTool to retrieve the current IP allowlist configuration for incident.io. Use when you need to check which IP addresses are allowed to access the incident.io API.

incident_io_list_schedule_entries_v2Tool to list schedule entries for a specific schedule in incident.io. Use when you need to retrieve on-call schedule entries for a given time window.

incident_io_list_schedules_v2Tool to list schedules from incident.io. Use when you need to retrieve on-call schedules with pagination support.

incident_io_list_status_pages_v2Tool to list status pages from incident.io. Use when you need to retrieve public or customer status pages with pagination support.

incident_io_list_users_v2Tool to list users in incident.io. Use when you need to retrieve users with their role information, filter by email or Slack user ID, with pagination support.

incident_io_list_workflows_v2Tool to list workflows from incident.io. Use when you need to retrieve configured workflows with pagination support.

incident_io_update_alert_attributes_v2Tool to update an alert attribute in incident.io. Use when you need to modify the configuration of an existing alert attribute such as changing its name, type, or whether it's required or an array.

incident_io_update_alert_sources_v2Tool to update an existing alert source configuration in incident.io. Use when you need to modify alert source properties such as name or template configuration including title, description, expressio

incident_io_update_catalog_entries_bulk_v3Tool to bulk update catalog entries in incident.io v3 API. Use when you need to create or update multiple catalog entries at once for a specific catalog type. This is more efficient than updating entr

incident_io_update_catalog_entries_v3Tool to update an existing catalog entry in incident.io using the v3 API. Use when you need to modify catalog entry properties such as name, attributes, aliases, or ranking. Note: All attribute values

incident_io_update_catalog_types_v3Tool to update a catalog type in incident.io V3 API. Use when you need to modify the configuration of an existing catalog type such as its name, description, annotations, or other properties.

incident_io_update_custom_field_option_v1Tool to update a custom field option in incident.io. Use when you need to modify the value, sort order, or parent custom field of an existing option.

incident_io_update_custom_fields_v1Tool to update an existing custom field configuration in incident.io. Use when you need to modify custom field properties such as name, description, visibility settings, or requirement rules.