incident.io MCP

Query incidents and alerts, check who is on call, and run operational analysis.

incident.io

Before you connect: what this server would do

A preview derived from this server’s definition — not a live run. Nothing runs and no key is sent until you connect. You connect directly to the provider’s own server with their sign-in.

Tools it can use (32)

incident_list
Search and browse incidents with filters.
incident_show
Full incident detail, optionally with post-mortem.
incident_create
Declare a new incident.
incident_update
Update status, severity, roles, custom fields.
incident_update_list
Full status-update history.
incident_stats
Aggregate counts and workload by dimension.
alert_list
Search and browse alerts.
alert_show
Full alert detail with linked incidents.
alert_source_list
Configured alert sources.
alert_stats
Alert counts with workload from linked incidents.
escalation_list
Search escalations (pages).
escalation_show
Escalation detail with transition history.
escalation_respond
Acknowledge or decline a real page.
escalation_path_list
List escalation paths.
escalation_path_show
Who would be paged at each level.
escalation_stats
Paging counts by path, priority, time of day.
schedule_list
List on-call schedules.
schedule_show
Schedule with current and upcoming shifts.
team_list
List teams.
team_show
Team with its paths, sources and schedules.
follow_up_create
Create a follow-up on an incident.
follow_up_list
List post-incident follow-ups.
catalog_type_list
List catalog types.
catalog_entry_list
Browse entries in a catalog type.
catalog_entry_show
Full catalog entry.
analysis_start
Start a structured operational analysis.
investigation_sync
Download a full investigation as an archive.
resource_show
Read org config, playbooks, telemetry datasources.
ask
AI agent for on-call and schedule questions.
ask_incident
AI agent for incident investigation and actions.
ask_telemetry
AI agent querying connected observability platforms.
feedback
Send feedback about the tools.

Credentials it will ask for (1)

incident.io API Key· optional
Used with: mcp.incident.io, api.incident.io

What FindAgent checked

It passed an automated security scan and a human review before it was published here.
Your client talks to this server directly, so FindAgent’s run-time protections — the prompt-injection deny-list on what you send, the secret-leak scan on every result, the credential-to-host binding, the approval gates — do not apply to what you send or receive here.

How FindAgent keeps servers safe

Connect over MCP — runs anywhere

incident.io MCP is a remote MCP server. Add its URL to any MCP-capable client — FindAgent lists it; it runs on the provider's own infrastructure.

1 · Choose your client

2 · Add the server URL

remote MCP

https://mcp.incident.io/mcp

ChatGPT (Plus / Pro): Settings → Connectors → add a remote MCP server, then paste the URL and approve it.

Open ChatGPT connectors

You add this server inside your client and approve it once — that in-client step is a security check, so there's no one-click button for it.

What you'll need — and where to get it

You give these to the server itself when it signs you in. They never pass through FindAgent, so we neither store them nor control where they go.

incident.io API Key · optional
Authenticates as a service actor and does not expire until deleted — the alternative to a 28-day OAuth grant.Get this from mcp.incident.io's account or API settings.Paste the value as a single line.Used with: mcp.incident.io, api.incident.io