MCP Incident Management

Unizo's Incident Management MCP Server provides a unified, agent-friendly interface for managing incidents across different platforms and organizational structures. Integrated via the Model Context Protocol (MCP), this server enables AI agents and LLM clients to interact with incident workflows, service monitoring, team coordination, and response tracking across multiple incident management platforms.

Designed for modern DevOps and SRE automation, this guide outlines installation, tool reference, and runtime configuration required to use the Unizo Incident Management MCP Server.

Overview

The Unizo Incident Management MCP Server enables seamless integration of incident management systems with AI agents through a standardized interface that abstracts the complexity of different incident tracking platforms.

Key Benefits

• Unified Incident Orchestration: Streamline incident response across organizations, services, and teams with a single API interface that normalizes workflows from different platforms
• AI Agent Compatibility: Built to integrate seamlessly with Claude, GPT, and other agents that speak the MCP protocol for automated incident triage and response
• Service-Aware Management: Navigate complex organizational hierarchies with service-based incident routing, team assignments, and escalation workflows
• Real-time Tracking: Monitor incident lifecycle from creation through resolution with comprehensive status tracking, priority management, and audit trails

Available Tools

Tool Reference

Tool Name	Description	Parameters
list_organizations	Retrieves all organizations available in the incident management system	Required: integration_id Optional: offset, limit, sort, correlation_id
list_services	Lists all services within a specific organization	Required: integration_id, organization_id, correlation_id Optional: offset, limit, sort
list_teams	Lists all teams responsible for a specific service	Required: integration_id, organization_id, service_id, correlation_id Optional: offset, limit, sort
list_incidents	Lists all incidents for a specific team and service	Required: integration_id, organization_id, service_id, team_id, correlation_id Optional: offset, limit, sort
create_incident	Creates a new incident with specified details and routing	Required: integration_id, organization_id, service_id, team_id, incident_data Optional: correlation_id

Installation & Setup

Prerequisites

• Node.js or Python runtime (based on your MCP proxy toolchain)
• MCP-compatible AI agent (e.g., Claude, GPT)
• Incident Management API credentials (see environment setup below)
• Valid integration IDs for your connected incident management platforms

Example MCP Server Setup (JSON)

{
  "mcpServers": {
    "unizo": {
      "command": "mcp-proxy",
      "args": ["http://172.184.130.51:8999/mcp"],
      "env": {
        "API_ACCESS_TOKEN": "your_account_token"
      }
    }
  }
}

Integration Tip

Integrate this Incident Management server alongside your Unizo EDR/XDR or SCM servers for complete threat-to-response automation and end-to-end incident orchestration.

Environment Variables

Variable	Description
API_ACCESS_TOKEN	Your Unizo-issued API key for secure MCP authentication

Client Integration Flow

1. Start the MCP Server

   • Use your orchestrator (Claude Desktop, GPT plugin, or equivalent)
   • Load the MCP JSON config with the unizo-incident-management target

2. Discover Organizational Structure

   • Call list_organizations to identify available organizations
   • Use get_organization for detailed organization information
   • Navigate to services with list_services and get_service

3. Identify Response Teams

   • Discover service ownership with list_teams
   • Get detailed team information via get_team

4. Manage Incident Lifecycle

   • List active incidents with list_incidents
   • Create new incidents using create_incident with proper routing
   • Track incident progress with get_incident
   • Update incident status and details via update_incident

The MCP server provides a consistent interface across different incident management platforms, allowing agents to use standardized tools regardless of the underlying service (Jira, GitHub, GitLab, etc.).

Observability & Logging

All incident management tool invocations are comprehensively logged by the MCP server with full agent context.

Early Access Program

The Unizo Incident Management MCP Server is currently available through our Early Access Program. All customers can gain priority access to these powerful incident management tools and receive dedicated implementation support.

Get Started Today

Reach out to our team to schedule a personalized demo and discuss integration options for your organization. Connect With Us