incident.io MCP Server

A GoLang implementation of an MCP (Model Context Protocol) server for incident.io, providing comprehensive tools to interact with the incident.io API. Built following industry-standard Go project layout patterns.
[!WARNING]
By the end of March 2026, we'll be deprecating this implementation in favour of our new remote MCP server.
Read more: https://docs.incident.io/ai/remote-mcp
If you'd like early access ahead of the public release, please get in touch.
π Quick Start
go run github.com/incident-io/incidentio-mcp-golang/cmd/mcp-server@latest
π Features
- β
Complete incident.io V2 API coverage including Custom Fields
- β
Workflow automation and management
- β
Alert routing and event handling
- β
Comprehensive test suite
- β
MCP protocol compliant
- β
Industry-standard Go project structure
- β
Clean, layered architecture (client β handlers β server)
π€ Using with Claude
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": "go",
"args":[
"run",
"github.com/incident-io/incidentio-mcp-golang/cmd/mcp-server@latest"
],
"env": {
"INCIDENT_IO_API_KEY": "your-api-key"
}
}
}
}
Or, if you'd prefer to run everything in Docker:
# Clone the repository
git clone https://github.com/incident-io/incidentio-mcp-golang.git
cd incidentio-mcp-golang
# Set up environment
cp .env.example .env
# Edit .env and add your incident.io API key
{
"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"
}
}
}
}
Incident Management
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
Follow-up Management
list_follow_ups - List follow-ups with optional filters
get_follow_up - Get details of a specific follow-up
Postmortem Management
list_postmortems - List postmortem documents with optional filters
get_postmortem - Get metadata for a specific postmortem document
get_postmortem_content - Get the full markdown content of a postmortem
Alert Management
list_alerts - List alerts with optional filters
get_alert - Get details of a specific alert
list_incident_alerts - List connections between incidents and alerts
create_alert_event - Create an alert event
list_alert_routes - List and manage alert routes
Workflow & Automation
list_workflows - List available workflows
get_workflow - Get workflow details
update_workflow - Update workflow configuration
Team & Roles
list_users - List organization users
list_available_incident_roles - List available incident roles
assign_incident_role - Assign roles to users
Catalog Management
list_catalog_types - List available catalog types
list_catalog_entries - List catalog entries
update_catalog_entry - Update catalog entries
Custom Fields
list_custom_fields - List all custom fields
get_custom_field - Get details of a specific custom field
search_custom_fields - Search for custom fields by name or type
create_custom_field - Create a new custom field
update_custom_field - Update custom field configuration
delete_custom_field - Delete a custom field
list_custom_field_options - List all custom field options
create_custom_field_option - Add a new option to a select field
π Example Usage
# 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"
"Show me all custom fields configured in incident.io"
"Search for custom fields related to 'priority'"
"Create a new custom field called 'Root Cause' with type single_select"
"List all postmortems for incident INC-123"
"Get the full content of the postmortem for our last major incident"
π Documentation
ποΈ Project Structure
This project follows industry-standard Go project layout:
βββ cmd/mcp-server/ # Main application entry point
βββ internal/
β βββ client/ # incident.io API client (HTTP layer)
β βββ handlers/ # MCP protocol handlers (adapter layer)
β βββ server/ # MCP server orchestration
βββ pkg/mcp/ # Public MCP types
βββ docs/ # Documentation
Design Philosophy:
internal/client: Pure HTTP API client for incident.io - reusable, testable
internal/handlers: MCP protocol adapters - converts MCP requests to API calls
internal/server: MCP server that orchestrates handlers and manages the protocol
π§ Troubleshooting
Common Issues
- 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 use
incident_id as the parameter name
Debug Mode
Enable debug logging by setting environment variables:
export MCP_DEBUG=1
export INCIDENT_IO_DEBUG=1
./start-mcp-server.sh
π€ Contributing
Contributions are welcome! Please see our Development Guide for details on setup, testing, and contribution guidelines.
π License
This project is licensed under the MIT License - see the LICENSE file for details.
π Acknowledgments