MCP1
Start with MCP1

incident.io MCP server

by incident.io

Incidents, alerts, on-call schedules and follow-ups.

One-click authEngineeringOperations & productivity
Add incident.io to MCP1incident.io docs

What it can do

  • Create and update incidents
  • Check on-call
  • Triage alerts
  • Track follow-ups

Through MCP1, every tool call is checked against your groups and rules, and recorded in the audit log.

How it connects

Authenticate with incident.io and approve MCP1. No token to copy; MCP1 keeps the connection sealed and refreshes it.

Team plan or higher. An admin turns it on in Settings, MCP, and allows MCP1 under Allowed redirect domains.

Endpoint
https://mcp.incident.io/mcp
Transport
Streamable HTTP
Docs
docs.incident.io

With MCP1

incident.io for the whole team, behind one URL

  1. 01

    Install it once

    An admin adds incident.io from the MCP1 catalog. Its authentication or token stays sealed in MCP1, never on a laptop.

  2. 02

    Decide who gets what

    Open it to groups, fully or read-only, and set rules per tool. Destructive tools can need an admin.

  3. 03

    Connect any client

    Claude, Cursor, ChatGPT, Codex and the rest connect one gateway URL and sign in with their own account.

More for engineering

See all engineering servers
  • GitHubEngineering

    Repositories, issues, pull requests, code search and Actions.

    Token
  • GitLabEngineering

    Projects, issues, merge requests and pipelines on GitLab.com.

    One-click auth
  • GitLab Self-ManagedGitLab

    Projects, issues, merge requests and pipelines on your own GitLab.

    One-click auth
  • LinearEngineering

    Find, create and update issues, projects and comments.

    One-click auth
  • SentryEngineering

    Search errors, triage issues and analyze performance.

    One-click auth
  • VercelEngineering

    Projects, deployments, runtime logs and the Vercel docs.

    One-click auth