waroom_create_incident
Declares an incident with a title, description, service_name and severity, optionally marked private or experimental.
LABSCO SUMMARY
It records the timings while you are still fixing the thing.
TTD, TTA, TTI, TTF and TTR are the numbers nobody reconstructs honestly afterwards. The slash commands read the phase from what the responder is actually doing — investigating, cause found, fixing, resolved — and update the incident as it happens, which is the only moment that data is real.
What it is
An MCP server for Waroom, an incident management platform. It creates and updates incidents, records the response-timing metrics, manages runbooks and action items, keeps per-service architecture context, and produces postmortems.
What you get
- Incidents — waroom_create_incident, waroom_get_incidents with filters, waroom_get_incident_details including the state document as Markdown, waroom_update_incident_severity, waroom_update_incident_status, waroom_update_incident_labels
- Metrics — waroom_create_incident_metrics records a response activity and updates TTD, TTA, TTI, TTF and TTR
- Postmortems — waroom_get_postmortems, waroom_create_postmortem, waroom_get_postmortem_template
- Services — waroom_get_services, waroom_get_service_architecture_context and waroom_update_service_architecture_context, so a responder starts with the system's shape in front of them
- Labels — waroom_get_service_labels, waroom_create_service_label, waroom_update_service_label, waroom_delete_service_label
- Runbooks — waroom_get_runbooks, waroom_get_runbook by namespace, waroom_update_runbook
- Action items — waroom_get_incident_action_items, waroom_create_incident_action_item, waroom_get_incident_action_item, waroom_update_incident_action_item, waroom_delete_incident_action_item, with waroom_get_users resolving the nickname needed to assign one
- Two Claude Code slash commands drive the flow — one opens a new incident from a service, the other picks up an existing one from a UUID or a URL — and both update status and metrics from what the responder is doing
- A waroom://about resource holds the full usage guide
Requirements
The npm package @topotal/waroom-mcp, run with npx and WAROOM_API_KEY in the environment; one claude mcp add command wires it in. If you use nodenv or nvm, give npx its full path. The project describes itself as experimental — stability and performance are not guaranteed. Tool descriptions and the slash-command documentation are written in Japanese.
Setup effort
One command plus a key — claude mcp add waroom-mcp --env WAROOM_API_KEY=<YOUR_WAROOM_API_KEY> -- npx @topotal/waroom-mcp
USE CASES
01
Opening an incident without leaving the terminal
Pick the service interactively, then create the incident and start tracking from the first message.
02
Picking up an incident from a link someone sent
Fetch it by UUID or URL, read the state document, and move it out of detected automatically.
03
Getting the response timings recorded correctly
Each activity stamps the metric it maps to, rather than being estimated after the fact.
04
Starting from the system's shape rather than guessing
The service's architecture context and the matching runbook, pulled up before the investigation starts.
05
Turning the incident into a postmortem
Start from the organisation's template, linked to the incidents it covers.
06
Assigning the follow-up work
Resolve the assignee's nickname, then file action items against the incident.
26 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
waroom_create_incident_action_item
Adds a new action item to an incident, with a title and status.
waroom_create_incident_metrics
Records a response activity against an incident with its triggered_at, advancing the TTD, TTA, TTI, TTF and TTR metrics.
waroom_create_postmortem
Creates a postmortem from a blob, with a title and status, tied to the incident_uuids it covers.
waroom_create_service_label
Creates a label on a service, with a name and a colour.
waroom_delete_incident_action_item
Deletes an action item from an incident, by action_item_uuid.
waroom_delete_service_label
Deletes a service label by label_uuid.
waroom_get_incident_action_item
Returns one action item of an incident, by action_item_uuid.
waroom_get_incident_action_items
Lists one incident's action items, paged with page and per_page.
waroom_get_incident_details
Returns one incident in full by incident_uuid, including its state document as Markdown.
waroom_get_incidents
Lists incidents, filterable by severities, status, service_names, label_names, commander_id, root_cause, a from/to window and includes_experimental, paged with page and per_page.
waroom_get_postmortem_template
Returns the organisation's postmortem template.
waroom_get_postmortems
Lists postmortems, paged with page and per_page.
waroom_get_runbook
Returns one runbook's detail, addressed by namespace.
waroom_get_runbooks
Lists runbooks, paged with page and per_page.
waroom_get_service_architecture_context
Returns the architecture context recorded for a given service_name.
waroom_get_service_labels
Lists the labels defined on a given service, paged with page and per_page.
waroom_get_services
Lists services, paged with page and per_page.
waroom_get_users
Lists the organisation's users, including the nickname used to name an action item's assignee.
waroom_update_incident_action_item
Updates an action item's title, its status — done or skipped among them — or its assignee.
waroom_update_incident_labels
Attaches or replaces the labels on an incident, given as label_uuids.
waroom_update_incident_severity
Changes an incident's severity.
waroom_update_incident_status
Changes an incident's status.
waroom_update_runbook
Updates the runbook at a namespace, changing its blob content or moving it to a new_namespace.
waroom_update_service_architecture_context
Writes a service's architecture context from a blob, updating the existing one or creating it where none exists.
waroom_update_service_label
Updates a service label's name or colour, addressed by label_uuid.
BEFORE YOU INSTALL
What to know first
Tools you get
26 tools when we connected.
Requires
- npx on PATH
- WAROOM_API_KEY in your environment
Where it runs
Both documented clients run the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 26 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
Claude Code
TERMINAL
claude mcp add waroom-mcp --env WAROOM_API_KEY=<YOUR_WAROOM_API_KEY> -- npx @topotal/waroom-mcpMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"waroom-mcp": {
"command": "npx",
"args": [
"@topotal/waroom-mcp"
],
"env": {
"WAROOM_API_KEY": "<YOUR_WAROOM_API_KEY>"
}
}
}
}
