> ## Documentation Index
> Fetch the complete documentation index at: https://www.truefoundry.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Set up incident.io MCP Server

> Enable incident.io Remote MCP and connect incident, alert, and on-call tools to TrueFoundry.

incident.io's Remote MCP server can create and update incidents, manage alerts, handle escalations, and interact with on-call schedules. You can connect it with per-user OAuth or an organization API key.

## Prerequisites

* A TrueFoundry account with permission to add MCP servers.
* An incident.io account with Remote MCP enabled.

## Enable Remote MCP

In incident.io, open **Settings** > **MCP** and enable the Remote MCP server. Copy the server URL shown by incident.io.

## Register with OAuth

In TrueFoundry, add the incident.io server URL as a remote MCP server and choose **OAuth2**. Add collaborators and save. Users should open the server's **Tools** section and click **Connect Now**; after OAuth succeeds, incident.io tools appear and can be tried from the **Agent Playground**.

## Register with an API Key

For automation, create an API key in incident.io under **Settings** > **API keys**. Grant only the roles the agent needs, such as incident creator or editor. In TrueFoundry, configure shared API key authentication for the incident.io MCP server.

## Security Notes

API keys act as a service actor and are not attributed to a person. Prefer OAuth for human-facing agents, rotate API keys periodically, and limit roles to the minimum required.