Source: https://manu-tests-all-orgs.docs-staging.pageloop.ai/integrations/mcp-store/incident-io-mcp-server

# 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](https://support.atomicwork.com/en/articles/14231031-incident-io-overview-and-setup).

### 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_manage` permission. You must grant this permission from the incident.io dashboard.

### Enable the remote MCP server

To allow Atomicwork to communicate with your incident.io tools, you must first enable the remote MCP server in your incident.io settings:

1. Log in to your incident.io dashboard and open **Settings**.
2. In the navigation menu, under **Extend**, click **MCP server**.
3. Check the button in the top-right corner. If it displays **Enable**, click it to turn the server on. If it displays **Disable**, the server is already active and no further action is required.

### Generate an API key

After enabling the MCP server, create a dedicated API key to authenticate the connection:

1. In your incident.io dashboard, open **Settings** and, under **Extend**, click **API keys**.
2. Click **New API key** to open the configuration dialog.
3. Enter a descriptive **Name** for the key (for example, "Atomicwork MCP Connection") to help you identify it later.
4. Under **Account-level permissions**, select the permissions your key requires. Use the search filter to find specific permissions, and grant only what is necessary to follow the principle of least privilege.
5. Click **Create**.
6. Copy the generated API key immediately and store it securely. The dashboard displays this key only once, and you cannot retrieve it later.

> \[!NOTE]
> Please note that the permissions you select while generating an API key determine the number of tools that AI Coworkers can utilize in Atomicwork.

### Connect the server in Atomicwork

Once you have your API key, complete the connection within your Atomicwork workspace:

1. Log in to Atomicwork and navigate to **Settings** > **MCP Store** > **incident.io**.
2. Click the **incident.io** tile and select **Connect**.
3. Paste your copied API key into the **API Key** field. Ensure there are no accidental leading or trailing spaces.
4. Click **Connect** to complete the setup. A list of all available incident.io tools will display on your screen.

### Manage tool access and permissions

To maintain a secure workspace, configure the specific capabilities your AI agents can access. The connected AI client can only perform actions that your API key permissions allow. We recommend starting with read-only access and adding write permissions as needed.

Review the common permissions and their capabilities below:

| Permission                       | Capabilities enabled                                                          |
| -------------------------------- | ----------------------------------------------------------------------------- |
| **Read-only baseline**           | View public incidents, organization configuration, statistics, and reporting. |
| **View all incident data**       | Read private incidents in addition to public ones.                            |
| **Create incidents**             | Allow the AI Coworker to open new incidents.                                  |
| **Edit incidents**               | Update incident status, severity, custom fields, and roles.                   |
| **View / Read schedules**        | View on-call schedules and active shifts.                                     |
| **Create and update schedules**  | Manage on-call schedules and create schedule overrides.                       |
| **View or manage catalog data**  | Read or edit catalog types and entries (such as services and teams).          |
| **Manage organization settings** | Change organization-level configuration, including custom fields.             |

You can also use team-scoped permissions to limit access to specific teams rather than the entire account. If you need to adjust permissions later, you can edit the API key in incident.io without recreating it.

### Next steps

After successfully connecting the incident.io MCP server, you can assign these tools to your AI workforce. Learn how to [set up an AI Coworker](https://support.atomicwork.com/en/articles/15259421-setting-up-an-ai-coworker) and configure granular tool access to protect your production environment.

---