- IDENTIFY
- CONTEXT
- VERIFY
- HUMAN
Short answer
Who is on call right now?
Your agent uses the Incident.io connection to pull active rotation data. It identifies the specific person currently responsible for a given schedule. You get the name and rotation details immediately.
Where the data goes.
Instant schedule visibility.
The AI pulls live rotation data to give you these specific outcomes.
IDENTIFY
Find the active responder
The agent scans active rotations to name the person currently on call. You get a direct answer instead of a link to a dashboard.
CONTEXT
Get rotation details
It pulls the specific schedule name and timeframes. This helps you understand exactly which rotation is currently active.
VERIFY
Confirm schedule status
The AI checks if a schedule is currently running or if a shift has ended. This prevents you from reaching out to the wrong person.
HUMAN
Escalate to the person
The AI provides the name, but you decide when to ping them or start an incident. It handles the lookup so you can handle the response.
The workflow
What your AI does when you ask about on-call.
The agent bridges the gap between your chat and your Incident.io data.
Fetch schedules
The agent looks up all available on-call rotations in your Incident.io account.
list_schedulesFilter active shifts
It narrows down the list to find the specific rotation that matches your request.
list_schedulesIdentify responder
The agent reads the current user assigned to the active slot.
list_schedulesReport findings
The agent translates the raw schedule data into a plain English answer for you.
list_schedules
Try it
Copy these to start.
Use these prompts to test the connection.
Starting points
Swap out the bracketed names for your actual rotation or team names.
Incident.io Connector
You're all set. Choose your MCP client and follow the setup instructions.
https://edge.vinkius.com/vk_preview_SYXytajPn2E8oSQTe6uxrJcvhwsU2x1pHkOPCe4y/mcpClaude Desktop
Follow the steps below to connect in seconds.
- 1In Claude Desktop, open Settings → Connectors.
- 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
- 3Click Add and start a new chat — Incident.io capabilities are ready to use.
{
"mcpServers": {
"incidentio-mcp": {
"url": "https://edge.vinkius.com/vk_preview_SYXytajPn2E8oSQTe6uxrJcvhwsU2x1pHkOPCe4y/mcp"
}
}
}Who is on call for the SRE rotation right now?
Which schedule is currently active for the database team?
Check the on-call status for the frontend rotation.
Who is the current responder for the primary incident schedule?
Claude
ChatGPT
Cursor
VS Code
Windsurf
Claude Code
JetBrains
Cline
Start here
Connect Incident.io once, then ask.
One connection gives your agent access to your schedules. Your credentials stay encrypted and secure.
Connect Incident.io to your AIFAQ
How the task behaves
- 01
Can the AI change who is on call?
No. The agent can only read existing schedule data. You must use the Incident.io UI to modify rotations or assignments.
- 02
Does the AI see my private messages?
No. The agent only accesses the specific schedule data provided by the tool.
- 03
Can I ask about past on-call shifts?
No. This specific capability is limited to querying active, current schedules.
- 04
Will the AI trigger an incident automatically?
No. The agent only identifies the person on call. It does not have the ability to create or trigger incidents.
- 05
How often does the AI see schedule updates?
The AI sees the most current data available in Incident.io at the moment you ask the question.
More questions about Incident.io? The Connector page answers them. See everything the Incident.io Connector can do
Connect Incident.io to Claude, Cursor, ChatGPT & more
