--- title: "incident.io MCP server for AI agents - actionlake" description: "Give Claude 326 incident.io actions through one MCP server: escalations, follow ups. Your agent never holds the credential. 100,000 calls a month free." canonical: https://actionlake.com/connectors/incident-io updated: 2026-10-22 --- Connectors · Service desk & support # incident.io MCP server for AI agents. actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to incident.io and the rest of your systems. It gives your agent 326 incident.io actions (148 reads, 128 writes and 50 that wait for a confirmation) and holds the incident.io credential itself, so the agent never does. It paces incident.io's limits and records every call. [Connect incident.io free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing) 100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you. `claude mcp add --transport http actionlake https://connect.actionlake.com/mcp` the first call ``` do { action: "incident_io.users.list", intent: "check which incident.io account is connected" } # List Users V2 · read · 1 upstream call ``` - 326 actions in one signed file - 148 read look, never change - 128 write create and update - 50 wait for a yes destructive, confirmed first Set up ## Connect incident.io in three steps. 1. 01 ### Add actionlake to Claude. Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us. `https://connect.actionlake.com/mcp` 2. 02 ### Connect incident.io. Bearer token. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead. actionlake stores what you paste write-only, sealed under your tenant's key. - `api_key` incident.io API key ``` account { op: "connections.requirements", service: "incident_io" } # free: exactly what to paste, and what is found for you ``` 3. 03 ### Make the first call. Check before a write. Ask in plain words; Claude picks the action. Before anything changes, `check` validates the call and prices it, for free. ``` do { action: "incident_io.users.list" } # list users v2 · read · 1 upstream call check { action: "incident_io.schedules.create", input: { … } } # free: inputs, permissions, cost and confirmations, nothing sent ``` incident.io at a glance **Sign-in** Bearer token. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead. **You provide** `api_key` **Limits we pace to** 1,200 calls a minute, per connection **API covered** Incident.io public API v1/v2/v3 (OpenAPI 3.0.3, openapiV3.json)`api.incident.io` **Built from** incident.io's documentation, read 22 October 2026[api.incident.io](https://api.incident.io/v1/openapiV3.json) [api-docs.incident.io](https://api-docs.incident.io/) **Service file** Version 1.0.0, signed (Ed25519) **Cached reads** 144 of 148 reads, for up to 5 minutes; a write clears what it affects **Shared entities** 4, so ask can line incident.io up with your other systems **Data** Processed and stored in Sydney, Australia. No US region yet Capabilities ## What an AI agent can do in incident.io. 326 actions in 92 areas. Every one carries its effect, so a key can allow the reads and hold the rest. - **148** read look, never change - **128** write create and update - **50** destructive wait for a confirmation 1. ### Escalations 7 3 read · 3 write · 1 destructive CheckEscalationPermissions Escalations V2 · Create Escalations V2 · List Escalations V2 · Show Escalations V2 2. ### Follow ups 7 2 read · 4 write · 1 destructive Create Follow-ups V3 · CreateFromLink Follow-ups V3 · List Follow-ups V3 · ConnectExternalIssue Follow-ups V3 3. ### Alert sources 6 3 read · 2 write · 1 destructive Create Alert Sources V2 · List Alert Sources V2 · Validate Alert Sources V2 · Show Alert Sources V2 4. ### Alerts 6 2 read · 4 write · 0 destructive List Alerts V2 · Show Alerts V2 · AddTags Alerts V2 · RemoveTags Alerts V2 5. ### API keys 6 2 read · 2 write · 2 destructive Create API Keys V1 · List API Keys V1 · Show API Keys V1 · Rotate API Keys V1 6. ### Catalog entries 6 2 read · 3 write · 1 destructive CreateEntry Catalog V3 · ListEntries Catalog V3 · BulkUpdateEntries Catalog V3 · ShowEntry Catalog V3 7. ### Catalog types 6 2 read · 3 write · 1 destructive CreateType Catalog V3 · ListTypes Catalog V3 · ShowType Catalog V3 · UpdateType Catalog V3 8. ### Catalog types V2 6 2 read · 3 write · 1 destructive CreateType Catalog V2 · ListTypes Catalog V2 · ShowType Catalog V2 · UpdateType Catalog V2 **84 more areas · 276 actions** - Follow ups V2 **6** - Incident templates **6** - Pay reports **6** - Schedules **6** - Secrets **6** - Actions **5** - Actions V2 **5** - Alert attributes **5** - Alert notes **5** - Alert routes **5** - Alert routes V2 **5** - Announcement rules **5** - Announcement templates **5** - Call route allowed callers **5** - Call route options **5** - Catalog entries V2 **5** - Custom field options **5** - Custom fields **5** - Custom fields V1 **5** - Escalation path templates **5** - Escalation paths **5** - Incident forms **5** - Incident roles **5** - Incident roles V1 **5** - Incident statuses **5** - Incidents **5** - Maintenance windows **5** - Pay config one off rules **5** - Pay config weekly rules **5** - Pay configs **5** - Policies **5** - Schedule overrides **5** - Schedule sync rules **5** - Schedule sync targets **5** - Severities **5** - Status page components **5** - Status page maintenances **5** - Workflows **5** - Policy findings **4** - Postmortem documents **4** - Schedule replicas **4** - Status page incidents **4** - Call routes **3** - Incident alerts **3** - Incident attachments **3** - Incident timeline items **3** - Incidents V1 **3** - Actions V1 **2** - Incident memberships **2** - Incident team memberships **2** - Incident timestamps **2** - Incident types **2** - Incident updates **2** - Ip allowlists **2** - On call notification pauses **2** - Status pages **2** - Teams **2** - User paging provider **2** - Users **2** - Workflow runs **2** - Alert events HTTP **1** - Alert tags **1** - Call sessions **1** - Call transcript entries **1** - Catalog resources **1** - Catalog resources V2 **1** - Heartbeat ping **1** - Identity **1** - Incident activity log entries **1** - Incident participant workloads **1** - Incident participants **1** - Incident relationships **1** - Ip ranges **1** - Postmortem document content **1** - Schedule entries **1** - Status page component availability **1** - Status page incident response incidents **1** - Status page incident updates **1** - Status page maintenance updates **1** - Status page retrospective incidents **1** - Status page structures **1** - Telemetry data sources **1** - User notification methods **1** - User notification rules **1** Top actions ## The incident.io API, shaped for agents. The ids your agent types, what each does, and the one name it shares with other systems. 43 of incident.io's 48 action names are shared with at least one other connector, so an agent learns them once. | Action | What it does | Effect | Same name in | | --- | --- | --- | --- | | `incident_io.users.list` List Users V2 | List Users V2. | read | `identity.user.list` 474 connectors | | `incident_io.teams.list` List Teams V3 | List Teams V3. | read | `identity.group.list` 262 connectors | | `incident_io.alerts.list` List Alerts V2 | List Alerts V2. | read | `monitoring.alert.list` 51 connectors | | `incident_io.users.get` Show Users V2 | Show Users V2. | read | `identity.user.get` 399 connectors | | `incident_io.incidents.list` List Incidents V2 | List Incidents V2. | read | `monitoring.incident.list` 19 connectors | | `incident_io.teams.get` Show Teams V3 | Show Teams V3. | read | `identity.group.get` 212 connectors | | `incident_io.schedules.list` List Schedules V2 | List Schedules V2. | read | `hr.on_call_schedule.list` 11 connectors | | `incident_io.schedules.create` Create Schedules V2 | Create Schedules V2. | write | `hr.on_call_schedule.create` 11 connectors | | `incident_io.escalation_paths.create` CreatePath Escalations V2 | CreatePath Escalations V2. | write | `hr.escalation_policy.create` 11 connectors | | `incident_io.escalation_paths.list` ListPaths Escalations V2 | ListPaths Escalations V2. | read | `hr.escalation_policy.list` 10 connectors | | `incident_io.incidents.create` Create Incidents V2 | Create Incidents V2. | write | `monitoring.incident.create` 13 connectors | | `incident_io.schedules.delete` Destroy Schedules V2 | Destroy Schedules V2. | destructive | `hr.on_call_schedule.delete` 11 connectors | Try it ## Prompts to paste into Claude. Each one names the incident.io actions it will call, so you know what it reads and what it changes before you send it. 1. Read read Which incident.io incidents are open, and how long has each been open? calls `incident_io.incidents.list` 2. Write write Create Schedules V2 in incident.io. Show me exactly what you will send before you save it. calls `incident_io.schedules.create` Governance for incident.io ## Destructive actions wait for a yes. 50 incident.io actions are destructive. The first 10: - Destroy Schedules V2 `incident_io.schedules.delete` - DestroyPath Escalations V2 `incident_io.escalation_paths.delete` - DestroyWorkflow Workflows V2 `incident_io.workflows.delete` - DestroyOverride Schedules V2 `incident_io.schedule_overrides.delete` - Destroy Status Page Components V2 `incident_io.status_page_components.delete` - Rotate Secrets V2 `incident_io.secrets.rotate` - Rotate API Keys V1 `incident_io.api_keys.rotate` - Delete Actions V3 `incident_io.actions.delete` - Destroy Secrets V2 `incident_io.secrets.delete` - Delete API Keys V1 `incident_io.api_keys.delete` A destructive action runs only with `confirm: true`. Under the `human` policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after. do incident_io.schedules.delete confirm_policy: **human** Destroy Schedules V2? **intent:** the user asked me to destroy Schedules V2 run suspended · waiting for a named person · key _incident-io-agent_ cannot confirm itself In the console, or from an emailed signed link. a key for this connector ``` account { op: "keys.create", name: "incident-io-agent", allowed_actions: ["incident_io.*"], cap_calls: 2000, confirm_policy: "human_for_writes", approval_rules: [ { match: "incident_io.schedules.delete", approver: "lead@example.com" }, { match: "incident_io.escalation_paths.delete", approver: "lead@example.com" }, { match: "incident_io.workflows.delete", approver: "lead@example.com" } ] } ``` Illustrative. Scoped to incident.io only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person. Cost ## What incident.io costs on actionlake. Every incident.io action is one upstream call, the only thing actionlake bills. Searching, `check`, `cost`, `account` and any call incident.io refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000. - 1 upstream call per action all 326 incident.io actions - 326 actions page each page of a long list is one call - 144 reads can be cached a cache hit costs nothing - 100,000 calls a month, free paid plans from US$49 a month for 250,000 [See pricing](https://actionlake.com/pricing) Action index ## Every incident.io action. 326 actions by area: the id your agent calls, what it does, and its effect. **Escalations 7** - `incident_io.escalations.check_permissions` CheckEscalationPermissions Escalations V2 read - `incident_io.escalations.create` Create Escalations V2 write - `incident_io.escalations.get` Show Escalations V2 read - `incident_io.escalations.list` List Escalations V2 read - `incident_io.escalations.cancel` CancelEscalation Escalations V2 destructive - `incident_io.escalations.reassign` ReassignEscalation Escalations V2 write - and 1 more in this area **Follow ups 7** - `incident_io.follow_ups.connect_external_issue` ConnectExternalIssue Follow-ups V3 write - `incident_io.follow_ups.create` Create Follow-ups V3 write - `incident_io.follow_ups.create_from_link` CreateFromLink Follow-ups V3 write - `incident_io.follow_ups.list` List Follow-ups V3 read - `incident_io.follow_ups.delete` Delete Follow-ups V3 destructive - `incident_io.follow_ups.get` Show Follow-ups V3 read - and 1 more in this area **Alert sources 6** - `incident_io.alert_sources.create` Create Alert Sources V2 write - `incident_io.alert_sources.get` Show Alert Sources V2 read - `incident_io.alert_sources.list` List Alert Sources V2 read - `incident_io.alert_sources.validate` Validate Alert Sources V2 read - `incident_io.alert_sources.delete` Delete Alert Sources V2 destructive - `incident_io.alert_sources.update` Update Alert Sources V2 write **Alerts 6** - `incident_io.alerts.add_tags` AddTags Alerts V2 write - `incident_io.alerts.get` Show Alerts V2 read - `incident_io.alerts.list` List Alerts V2 read - `incident_io.alerts.remove_tags` RemoveTags Alerts V2 write - `incident_io.alerts.resolve` Resolve Alerts V2 write - `incident_io.alerts.set_tags` SetTags Alerts V2 write **API keys 6** - `incident_io.api_keys.create` Create API Keys V1 write - `incident_io.api_keys.get` Show API Keys V1 read - `incident_io.api_keys.list` List API Keys V1 read - `incident_io.api_keys.rotate` Rotate API Keys V1 destructive - `incident_io.api_keys.delete` Delete API Keys V1 destructive - `incident_io.api_keys.update` Update API Keys V1 write **Catalog entries 6** - `incident_io.catalog_entries.bulk_update` BulkUpdateEntries Catalog V3 write - `incident_io.catalog_entries.create` CreateEntry Catalog V3 write - `incident_io.catalog_entries.get` ShowEntry Catalog V3 read - `incident_io.catalog_entries.list` ListEntries Catalog V3 read - `incident_io.catalog_entries.delete` DestroyEntry Catalog V3 destructive - `incident_io.catalog_entries.update` UpdateEntry Catalog V3 write **Catalog types 6** - `incident_io.catalog_types.create` CreateType Catalog V3 write - `incident_io.catalog_types.get` ShowType Catalog V3 read - `incident_io.catalog_types.list` ListTypes Catalog V3 read - `incident_io.catalog_types.update` UpdateType Catalog V3 write - `incident_io.catalog_types.delete` DestroyType Catalog V3 destructive - `incident_io.catalog_types.update_schema` UpdateTypeSchema Catalog V3 write **Catalog types V2 6** - `incident_io.catalog_types_v2.create` CreateType Catalog V2 write - `incident_io.catalog_types_v2.get` ShowType Catalog V2 read - `incident_io.catalog_types_v2.list` ListTypes Catalog V2 read - `incident_io.catalog_types_v2.update` UpdateType Catalog V2 write - `incident_io.catalog_types_v2.delete` DestroyType Catalog V2 destructive - `incident_io.catalog_types_v2.update_schema` UpdateTypeSchema Catalog V2 write **Follow ups V2 6** - `incident_io.follow_ups_v2.connect_external_issue` ConnectExternalIssue Follow-ups V2 write - `incident_io.follow_ups_v2.create` Create Follow-ups V2 write - `incident_io.follow_ups_v2.get` Show Follow-ups V2 read - `incident_io.follow_ups_v2.list` List Follow-ups V2 read - `incident_io.follow_ups_v2.delete` Delete Follow-ups V2 destructive - `incident_io.follow_ups_v2.update` Update Follow-ups V2 write **Incident templates 6** - `incident_io.incident_templates.create` Create Incident Templates V1 write - `incident_io.incident_templates.get` Show Incident Templates V1 read - `incident_io.incident_templates.list` List Incident Templates V1 read - `incident_io.incident_templates.validate` Validate Incident Templates V1 read - `incident_io.incident_templates.delete` Destroy Incident Templates V1 destructive - `incident_io.incident_templates.update` Update Incident Templates V1 write **Pay reports 6** - `incident_io.pay_reports.create` Create Pay Reports V2 write - `incident_io.pay_reports.get` Show Pay Reports V2 read - `incident_io.pay_reports.list` List Pay Reports V2 read - `incident_io.pay_reports.publish` Publish Pay Reports V2 write - `incident_io.pay_reports.delete` Destroy Pay Reports V2 destructive - `incident_io.pay_reports.unpublish` Unpublish Pay Reports V2 write **Schedules 6** - `incident_io.schedules.create` Create Schedules V2 write - `incident_io.schedules.get` Show Schedules V2 read - `incident_io.schedules.list` List Schedules V2 read - `incident_io.schedules.update` Update Schedules V2 write - `incident_io.schedules.delete` Destroy Schedules V2 destructive - `incident_io.schedules.preview_entries` PreviewScheduleEntries Schedules V2 read **Secrets 6** - `incident_io.secrets.create` Create Secrets V2 write - `incident_io.secrets.get` Show Secrets V2 read - `incident_io.secrets.list` List Secrets V2 read - `incident_io.secrets.rotate` Rotate Secrets V2 destructive - `incident_io.secrets.delete` Destroy Secrets V2 destructive - `incident_io.secrets.update` Update Secrets V2 write **Actions 5** - `incident_io.actions.create` Create Actions V3 write - `incident_io.actions.get` Show Actions V3 read - `incident_io.actions.list` List Actions V3 read - `incident_io.actions.update` Update Actions V3 write - `incident_io.actions.delete` Delete Actions V3 destructive **Actions V2 5** - `incident_io.actions_v2.create` Create Actions V2 write - `incident_io.actions_v2.get` Show Actions V2 read - `incident_io.actions_v2.list` List Actions V2 read - `incident_io.actions_v2.update` Update Actions V2 write - `incident_io.actions_v2.delete` Delete Actions V2 destructive **Alert attributes 5** - `incident_io.alert_attributes.create` Create Alert Attributes V2 write - `incident_io.alert_attributes.get` Show Alert Attributes V2 read - `incident_io.alert_attributes.list` List Alert Attributes V2 read - `incident_io.alert_attributes.update` Update Alert Attributes V2 write - `incident_io.alert_attributes.delete` Destroy Alert Attributes V2 destructive **Alert notes 5** - `incident_io.alert_notes.create` Create Alert Notes V1 write - `incident_io.alert_notes.get` Show Alert Notes V1 read - `incident_io.alert_notes.list` List Alert Notes V1 read - `incident_io.alert_notes.update` Update Alert Notes V1 write - `incident_io.alert_notes.delete` Delete Alert Notes V1 destructive **Alert routes 5** - `incident_io.alert_routes.create` Create Alert Routes V3 write - `incident_io.alert_routes.get` Show Alert Routes V3 read - `incident_io.alert_routes.list` List Alert Routes V3 read - `incident_io.alert_routes.update` Update Alert Routes V3 write - `incident_io.alert_routes.delete` Delete Alert Routes V3 destructive **Alert routes V2 5** - `incident_io.alert_routes_v2.create` Create Alert Routes V2 write - `incident_io.alert_routes_v2.get` Show Alert Routes V2 read - `incident_io.alert_routes_v2.list` List Alert Routes V2 read - `incident_io.alert_routes_v2.update` Update Alert Routes V2 write - `incident_io.alert_routes_v2.delete` Delete Alert Routes V2 destructive **Announcement rules 5** - `incident_io.announcement_rules.create` Create Announcement Rules V2 write - `incident_io.announcement_rules.get` Show Announcement Rules V2 read - `incident_io.announcement_rules.list` List Announcement Rules V2 read - `incident_io.announcement_rules.update` Update Announcement Rules V2 write - `incident_io.announcement_rules.delete` Destroy Announcement Rules V2 destructive **Announcement templates 5** - `incident_io.announcement_templates.create` Create Announcement Templates V2 write - `incident_io.announcement_templates.get` Show Announcement Templates V2 read - `incident_io.announcement_templates.list` List Announcement Templates V2 read - `incident_io.announcement_templates.update` Update Announcement Templates V2 write - `incident_io.announcement_templates.delete` Destroy Announcement Templates V2 destructive **Call route allowed callers 5** - `incident_io.call_route_allowed_callers.create` CreateAllowedCaller Call Routes V2 write - `incident_io.call_route_allowed_callers.get` ShowAllowedCaller Call Routes V2 read - `incident_io.call_route_allowed_callers.list` ListAllowedCallers Call Routes V2 read - `incident_io.call_route_allowed_callers.update` UpdateAllowedCaller Call Routes V2 write - `incident_io.call_route_allowed_callers.delete` DestroyAllowedCaller Call Routes V2 destructive **Call route options 5** - `incident_io.call_route_options.create` CreateOption Call Routes V2 write - `incident_io.call_route_options.get` ShowOption Call Routes V2 read - `incident_io.call_route_options.list` ListOptions Call Routes V2 read - `incident_io.call_route_options.update` UpdateOption Call Routes V2 write - `incident_io.call_route_options.delete` DestroyOption Call Routes V2 destructive **Catalog entries V2 5** - `incident_io.catalog_entries_v2.create` CreateEntry Catalog V2 write - `incident_io.catalog_entries_v2.get` ShowEntry Catalog V2 read - `incident_io.catalog_entries_v2.list` ListEntries Catalog V2 read - `incident_io.catalog_entries_v2.update` UpdateEntry Catalog V2 write - `incident_io.catalog_entries_v2.delete` DestroyEntry Catalog V2 destructive **Custom field options 5** - `incident_io.custom_field_options.create` Create Custom Field Options V1 write - `incident_io.custom_field_options.get` Show Custom Field Options V1 read - `incident_io.custom_field_options.list` List Custom Field Options V1 read - `incident_io.custom_field_options.update` Update Custom Field Options V1 write - `incident_io.custom_field_options.delete` Delete Custom Field Options V1 destructive **Custom fields 5** - `incident_io.custom_fields.create` Create Custom Fields V2 write - `incident_io.custom_fields.get` Show Custom Fields V2 read - `incident_io.custom_fields.list` List Custom Fields V2 read - `incident_io.custom_fields.update` Update Custom Fields V2 write - `incident_io.custom_fields.delete` Delete Custom Fields V2 destructive **Custom fields V1 5** - `incident_io.custom_fields_v1.create` Create Custom Fields V1 write - `incident_io.custom_fields_v1.get` Show Custom Fields V1 read - `incident_io.custom_fields_v1.list` List Custom Fields V1 read - `incident_io.custom_fields_v1.update` Update Custom Fields V1 write - `incident_io.custom_fields_v1.delete` Delete Custom Fields V1 destructive **Escalation path templates 5** - `incident_io.escalation_path_templates.create` Create Escalation Path Templates V2 write - `incident_io.escalation_path_templates.get` Show Escalation Path Templates V2 read - `incident_io.escalation_path_templates.list` List Escalation Path Templates V2 read - `incident_io.escalation_path_templates.update` Update Escalation Path Templates V2 write - `incident_io.escalation_path_templates.delete` Destroy Escalation Path Templates V2 destructive **Escalation paths 5** - `incident_io.escalation_paths.create` CreatePath Escalations V2 write - `incident_io.escalation_paths.get` ShowPath Escalations V2 read - `incident_io.escalation_paths.list` ListPaths Escalations V2 read - `incident_io.escalation_paths.update` UpdatePath Escalations V2 write - `incident_io.escalation_paths.delete` DestroyPath Escalations V2 destructive **Incident forms 5** - `incident_io.incident_forms.create` Create Incident Forms V3 write - `incident_io.incident_forms.get` Show Incident Forms V3 read - `incident_io.incident_forms.list` List Incident Forms V3 read - `incident_io.incident_forms.update` Update Incident Forms V3 write - `incident_io.incident_forms.delete` Delete Incident Forms V3 destructive Incident roles **5** Incident roles V1 **5** Incident statuses **5** Incidents **5** Maintenance windows **5** Pay config one off rules **5** Pay config weekly rules **5** Pay configs **5** Policies **5** Schedule overrides **5** Schedule sync rules **5** Schedule sync targets **5** Severities **5** Status page components **5** Status page maintenances **5** Workflows **5** Policy findings **4** Postmortem documents **4** Schedule replicas **4** Status page incidents **4** Call routes **3** Incident alerts **3** Incident attachments **3** Incident timeline items **3** Incidents V1 **3** Actions V1 **2** Incident memberships **2** Incident team memberships **2** Incident timestamps **2** Incident types **2** Incident updates **2** Ip allowlists **2** On call notification pauses **2** Status pages **2** Teams **2** User paging provider **2** Users **2** Workflow runs **2** Alert events HTTP **1** Alert tags **1** Call sessions **1** Call transcript entries **1** Catalog resources **1** Catalog resources V2 **1** Heartbeat ping **1** Identity **1** Incident activity log entries **1** Incident participant workloads **1** Incident participants **1** Incident relationships **1** Ip ranges **1** Postmortem document content **1** Schedule entries **1** Status page component availability **1** Status page incident response incidents **1** Status page incident updates **1** Status page maintenance updates **1** Status page retrospective incidents **1** Status page structures **1** Telemetry data sources **1** User notification methods **1** User notification rules **1** This index shows a sample of each area. All 326 actions, with their inputs and prices, are in the [catalogue](https://actionlake.com/console/catalogue), which a free sandbox key can search. Questions ## The incident.io MCP server, answered. **Is there an incident.io MCP server for Claude?** Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 326 incident.io actions across escalations, follow ups, alert sources and alerts, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by incident.io. **What do I need to connect incident.io?** Incident.io API key. The free call account { op: "connections.requirements", service: "incident_io" } lists exactly what to paste. **Can an AI agent delete or change things in incident.io?** Only if its key allows it, and only with an explicit confirmation. 50 incident.io actions are destructive, including destroy Schedules V2, destroyPath Escalations V2 and destroyWorkflow Workflows V2. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it. **Will an AI agent use up my incident.io API limit?** actionlake paces every call to the limits in the incident.io service file: 1,200 calls a minute per connection. Repeated reads are answered from cache (144 incident.io actions can be), which never reaches incident.io. **What does an incident.io action cost?** One upstream call, the only unit actionlake bills. A list that pages bills one call per page (326 incident.io actions page). Cache hits, searches, dry runs and calls incident.io refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000. **Which incident.io API does it cover?** The incident.io public API v1/v2/v3 (OpenAPI 3.0.3, openapiV3.json) at api.incident.io. It is built from incident.io's documentation as read on 22 October 2026. 326 actions in 92 areas, each one in the signed service file (version 1.0.0). **Does actionlake keep my incident.io data, and where?** actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to 5 minutes, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your incident.io credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models. **Which AI clients can use it?** Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names. ## More connectors like incident.io Shares the most action names with - [FireHydrant 31](https://actionlake.com/connectors/firehydrant) - [ilert 27](https://actionlake.com/connectors/ilert) - [Rootly 21](https://actionlake.com/connectors/rootly) - [Better Stack Uptime 21](https://actionlake.com/connectors/better-stack-uptime) - [Squadcast 21](https://actionlake.com/connectors/squadcast) - [Zenduty 18](https://actionlake.com/connectors/zenduty) Joins with, on shared entities - [Palo Alto Networks Cortex XDR 4](https://actionlake.com/connectors/palo-alto-networks-cortex-xdr) - [Commvault Cloud 3](https://actionlake.com/connectors/commvault-cloud) - [MongoDB Atlas 3](https://actionlake.com/connectors/mongodb-atlas) - [Mitti 3](https://actionlake.com/connectors/mitti) - [Sophos Central 3](https://actionlake.com/connectors/sophos-central) - [StrangeBee TheHive 3](https://actionlake.com/connectors/strangebee-thehive) Browse - [All Service desk & support connectors](https://actionlake.com/connectors/category/service-desk-and-support) - [All connectors](https://actionlake.com/connectors) - [How actionlake compares](https://actionlake.com/compare) actionlake is independent. It is not made or endorsed by incident.io; the name is the vendor's own. Counts are from the incident.io service file, version 1.0.0. ## Give your agent incident.io today. [Connect incident.io free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing) Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free. --- Source: https://actionlake.com/connectors/incident-io More: https://actionlake.com/llms.txt