Hosting

Vendor-hosted remote MCP service

Transport

Streamable HTTP

Endpoint

https://mcp.incident.io/mcp

Authentication

OAuth for interactive use; API key documented for internal/automated integrations.

Requirements

• Paid incident.io workspace; the vendor documents access for paid accounts.
• Organization administrator must enable the server under Settings → MCP.
• MCP client supporting remote HTTP MCP and OAuth.

Setup steps

1. In incident.io open Settings → MCP and enable the server for the organization.
2. Add https://mcp.incident.io/mcp to the client and complete the browser OAuth flow.
3. Inspect tools/list and begin with a read-only incident or on-call query.
4. Some tools create or modify incidents, pages, investigations, and schedules; confirm before executing those actions.

The remote server exposes a broad, evolving toolset. The five names stored here are representative documented examples, not a complete count. The macOS app has local MCP support with additional investigation/UI features.

• incident_stats

  Incident history and operational statistics.

  01
• status_page_update

  Draft a status page update; publishing remains a human action.

  02
• analysis_start

  Start a structured operational analysis.

  03
• incident_show

  Retrieve incident details.

  04
• investigation_start

  Start an incident investigation.

  05

This server’s available tools can vary by account, permissions, or configuration. The list shown is not its full runtime catalog.

• Public beta or release maturity may change as vendor documentation updates.
• Several actions modify incident operations; status-page publication is intentionally a human action.
• Connection and functionality were not tested in this research pass.

• official vendor setup and tool reference

  incident.io documents the endpoint, OAuth/API-key options, enablement, capabilities, and representative tool names.

• official vendor announcement

  incident.io announces its supported remote MCP server.

• official website favicon

  Selected asset visually reviewed in light and dark contact sheets; accepted at A/B — vendor favicon visually confirmed as product/company mark. Original response decoded as png, 192×192; local PNG verified at 160×160.

• official remote server reference

  Current docs describe broad remote incident, alert, on-call, escalation, action, follow-up, and status-draft capabilities; shown names are examples, not a complete fixed tool list.

Documentation checked 2026-10-28T00:00:00Z. Connection has not been runtime tested.