Incident.io MCP Server
incident.io MCP server
Connect the incident.io MCP server
Connect incident.io MCP to Atomicwork to automate incident response and manage on-call schedules.
Integrate the incident.io Model Context Protocol (MCP) server with Atomicwork to equip your AI Coworkers with incident management, on-call scheduling, and catalog tools. By connecting this server, your AI Coworkers can securely interact with your incident.io environment to automate incident response, look up on-call shifts, and update catalog data.
This article explains how to enable the incident.io MCP server, generate an API key, and connect it to your Atomicwork workspace. API key authentication acts as a service actor rather than a specific individual. If you need actions tied to individual user permissions, use OAuth authentication instead. For standard workflow automation, see our guide on the incident.io App Store integration.
Verify your prerequisites
Before you begin the setup, ensure you have the following permissions and plan requirements:
- Atomicwork admin access: You need organization admin permissions in Atomicwork to access the MCP Store.
- incident.io plan: An active incident.io account on a Team, Pro, or Enterprise plan.
- incident.io admin access: Admin-level access (or a custom role) in incident.io that includes the
api_keys_managepermission. You must grant this permission from the incident.io dashboard.
