MCP.so
Sign In
I

incident.io MCP Server

@incident.io

Basic information

Transport

Streamable HTTP

Authentication

OAuth

Category

Cloud & Infrastructure

Author

incident.io

About incident.io MCP Server

incident.io is an incident management platform covering response, on-call, and status pages. Its remote MCP server lets assistants declare and triage incidents, acknowledge pages, check on-call schedules, and track follow-ups across the whole workspace.

Connection details

https://mcp.incident.io/mcp

Setup

claude mcp add incident-io --transport http https://mcp.incident.io/mcp

incident.io MCP Server tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

This server requires authentication. Tool discovery may require signing in or credentials from the provider.

Fetch the live tool list directly from this server's endpoint using the button above.

Frequently asked questions

1

What is the incident.io remote MCP server?

The incident.io remote MCP server is a hosted Model Context Protocol endpoint at https://mcp.incident.io/mcp, so AI assistants can connect to it without installing or running anything locally.

2

How do I connect to the incident.io MCP server?

Add the endpoint https://mcp.incident.io/mcp to any MCP-compatible client such as Claude Code, Cursor, or VS Code. The setup snippets on this page configure each client in one step.

3

Does the incident.io MCP server require authentication?

Yes. incident.io uses OAuth: the first time you connect, your MCP client opens a browser window to sign in and authorize access, then reuses the credentials for future sessions.

4

Which transport does the incident.io MCP server use?

incident.io exposes a Streamable HTTP endpoint, the transport used by remote MCP servers and supported by all major MCP clients.

Comments