- Home
- MCP servers
- Waroom
Waroom
- javascript
1
GitHub Stars
javascript
Language
6 months ago
First Indexed
2 months ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
Installation
Add the following to your MCP client configuration file.
Configuration
View docs{
"mcpServers": {
"topotal-waroom-mcp": {
"command": "npx",
"args": [
"@topotal/waroom-mcp"
],
"env": {
"WAROOM_API_KEY": "YOUR_API_KEY"
}
}
}
}The Waroom MCP server provides a standardized Model Context Protocol interface to access Waroom data—such as incidents, postmortems, services, and labels—through a structured, extensible API. This makes it easier to automate incident response, track work, and integrate Waroom data into your tooling and workflows.
How to use
You interact with the Waroom MCP server through an MCP client or tooling that supports the MCP protocol. The server exposes endpoints for creating and updating incidents, retrieving incident and postmortem data, managing services and labels, and initiating guided incident workflows. Use your MCP client to start an incident, respond to an incident, or fetch contextual information about services and architectures. The system automatically tracks stages of work from investigation through resolution, updating metrics and status as you progress.
How to install
Prerequisites: ensure you have a suitable runtime for running MCP servers in your environment. The setup described here uses a local, command-based approach that runs via a package runner.
# Recommended for usage with MCP tooling that executes local commands
# Start the MCP server via the inline command shown in the configuration snippet
npx @topotal/waroom-mcp
Configuration and startup details
Configure your MCP client to know how to start the Waroom MCP server and pass the required API key. You will provide the API key to authorize requests to Waroom.
{
"mcpServers": {
"waroom-mcp": {
"command": "npx",
"args": ["@topotal/waroom-mcp"],
"env": {
"WAROOM_API_KEY": "your-api-key"
}
}
}
}
Notes on using Claude Code and Claude Desktop
If you are using Claude Code, add the MCP server with your API key as an environment variable and run the MCP server via the provided command.
claude mcp add waroom-mcp --env WAROOM_API_KEY=your-api-key -- npx @topotal/waroom-mcp
Usage with Claude Desktop
Create or update the MCP server entry in Claude Desktop’s configuration so the Waroom features are available within Claude’s workflow.
{
"mcpServers": {
"waroom-mcp": {
"command": "npx",
"args": ["@topotal/waroom-mcp"],
"env": {
"WAROOM_API_KEY": "your-api-key"
}
}
}
}
Available tools
waroom_create_incident
Create a new incident by specifying the service name, title, severity, and other relevant fields.
waroom_get_incidents
Retrieve a paginated list of incidents with support for paging through results.
waroom_get_incident_details
Fetch detailed information for a specific incident by its UUID.
waroom_update_incident_severity
Update the severity level of a given incident.
waroom_update_incident_status
Update the status of a given incident.
waroom_create_incident_metrics
Create or update incident metrics such as TTD, TTA, TTI, TTF, and TTR.
waroom_update_incident_labels
Add or update labels on a specific incident.
waroom_get_postmortems
List postmortems with pagination support.
waroom_create_postmortem
Create a new postmortem record.
waroom_get_postmortem_template
Retrieve a postmortem template for standardized input.
waroom_get_services
Fetch the list of services.
waroom_get_service_architecture_context
Obtain architecture context for a specific service.
waroom_get_service_labels
Get labels associated with a specific service.
waroom_create_service_label
Create a new label for a service.
waroom_update_service_label
Update an existing label on a service.
waroom_delete_service_label
Delete a label from a service.