Repository files navigation

A GoLang implementation of an MCP (Model Context Protocol) server for incident.io, providing tools to interact with the incident.io V2 API.

⚠️Fair warning!⚠️
This repository is largely vibe-coded and unsupported. Built by our CMO and an enterprising Solutions Engineer with questionable coding practices but undeniable enthusiasm. Use at your own risk! 🚀

# Clone the repositorygit clone https://github.com/incident-io/incidentio-mcp-golang.gitcd incidentio-mcp-golang# Set up environmentcp .env.example .env# Edit .env and add your incident.io API key# Build and rungo build -o bin/mcp-server ./cmd/mcp-server./start-mcp-server.sh

• ✅ Complete incident.io V2 API coverage
• ✅ Workflow automation and management
• ✅ Alert routing and event handling
• ✅ Comprehensive test suite
• ✅ MCP protocol compliant
• ✅ Clean, modular architecture

Add to your Claude Desktop configuration:

macOS:~/Library/Application Support/Claude/claude_desktop_config.json
Windows:%APPDATA%\Claude\claude_desktop_config.json

{"mcpServers": {"incidentio": {"command":"/path/to/incidentio-mcp-golang/start-mcp-server.sh","env": {"INCIDENT_IO_API_KEY":"your-api-key"      }    }  }}

Or, if you'd prefer to run everything in Docker:

{"mcpServers": {"incidentio": {"command":"docker-compose","args": ["-f","/path/to/docker-compose.yml","run","--rm","-T","mcp-server"],"env": {"INCIDENT_IO_API_KEY":"your-api-key"        }      }    }}

• list_incidents - List incidents with optional filters
• get_incident - Get details of a specific incident
• create_incident - Create a new incident
• update_incident - Update an existing incident
• close_incident - Close an incident with proper workflow
• create_incident_update - Post status updates to incidents

• list_alerts - List alerts with optional filters
• get_alert - Get details of a specific alert
• list_alerts_for_incident - List alerts for an incident
• create_alert_event - Create an alert event
• list_alert_routes - List and manage alert routes

• list_workflows - List available workflows
• get_workflow - Get workflow details
• update_workflow - Update workflow configuration

• list_users - List organization users
• list_available_incident_roles - List available incident roles
• assign_incident_role - Assign roles to users

• list_catalog_types - List available catalog types
• list_catalog_entries - List catalog entries
• update_catalog_entry - Update catalog entries

# Through Claude or another MCP client"Show me all active incidents""Create a new incident called 'Database performance degradation' with severity high""List alerts for incident INC-123""Assign John Doe as incident lead for INC-456""Update the Payments service catalog entry with new team information"

• Development Guide - Setup, testing, and contribution guidelines
• Configuration Guide - Environment variables and deployment options
• Contributing Guide - How to contribute to the project
• Testing Guide - Testing documentation and best practices
• Deployment Guide - Deployment instructions and considerations
• Code of Conduct - Community guidelines and standards

• 404 errors: Ensure incident IDs are valid and exist in your instance
• Authentication errors: Verify your API key is correct and has proper permissions
• Parameter errors: All incident-related tools useincident_id as the parameter name

Enable debug logging by setting environment variables:

export MCP_DEBUG=1export INCIDENT_IO_DEBUG=1./start-mcp-server.sh

Contributions are welcome! Please see ourDevelopment Guide for details on setup, testing, and contribution guidelines.

This project is licensed under the MIT License - see theLICENSE file for details.

• Built with theModel Context Protocol specification
• Powered byincident.io API
• Created with assistance from Claude