incident-io-mcp-server
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@incident-io-mcp-servershow me the latest incidents"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Incident.io MCP Server
A Model Context Protocol server for Incident.io integration.
Installation from GitHub
# Install directly from GitHub
npm install -g github:stuartphilp/incident-io-mcp-server
# Or clone and install locally
git clone https://github.com/stuartphilp/incident-io-mcp-server.git
cd incident-io-mcp-server
npm install
npm run buildRelated MCP server: pagerduty-mcp
Usage
Run the server:
# If installed globally
incident-io-mcp-server
# Or if installed locally
node ./dist/index.jsRequired environment variables:
API_KEY: Your Incident.io API key
Optional environment variables:
PORT: Server port (default: 3000)
Configuration
Example MCP configuration for global installation:
{
"mcpServers": {
"incident-io": {
"command": "incident-io-mcp-server",
"env": {
"API_KEY": "your-api-key-here",
"PORT": "3000"
}
}
}
}Example MCP configuration for local installation:
{
"mcpServers": {
"incident-io": {
"command": "node",
"args": ["./node_modules/incident-io-mcp-server/dist/index.js"],
"env": {
"API_KEY": "your-api-key-here",
"PORT": "3000"
}
}
}
}Endpoints
GET /health: Health check endpointGET /mcp/incidents: Get latest incidentsGET /mcp/severities: Get available severitiesPOST /mcp/incidents: Create a new incident
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
No tool schema history has been recorded yet.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
Manage incidents and on-call: list/create/update incidents, who is on call, on-call overrides.
Monitor websites, APIs, and servers: create monitors, triage incidents, and query uptime stats.
Read incidents, services, teams, on-call schedules; acknowledge, resolve and note incidents.
Manage incident alerts, events, and workflows with custom automations
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables SRE operations through natural language, providing tools to query SLO status, fetch runbooks, query alerts, and manage incidents with audit logging and latency tracking.-
- AlicenseNot gradedqualityCmaintenanceEnables PagerDuty incident response operations including listing incidents, acknowledging and resolving incidents, looking up on-call schedules, and listing services.MIT
- FlicenseNot gradedqualityDmaintenanceEnables management of Atlassian Statuspage incidents, components, and subscribers through natural language.-
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with PagerDuty services, incidents, schedules, and on-call management through natural language.-
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/stuartphilp/incident-io-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server