Waroom MCP
The Waroom MCP server provides a standardized protocol to interact with the Waroom API and fetch incident and postmortem information.
You can:
Retrieve a paginated list of incidents (
waroom_get_incidents)Get details of a specific incident by UUID (
waroom_get_incident_details)Retrieve a paginated list of postmortems (
waroom_get_postmortems)
Click on "Deploy 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., "@Waroom MCP show me the latest incidents for the payment service"
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.
Waroom MCP
[!CAUTION] This is still an experimental project and there are no guarantees of stability or performance. Use with caution.
This project is a Model Context Protocol (MCP) server for interacting with the Warroom API, allowing you to get various information from Warroom using a standardized protocol.
overview
The Waroom MCP Server provides a structured way to access the Waroom API endpoints, supporting a variety of functions, including retrieving incident and postmortem information.
Related MCP server: Notion MCP Server
How to use
To start the server, set the necessary environment variables:
export WAROOM_API_KEY=your_api_keyNext, run the following command:
npx @topotal/waroom-mcpThis will start the MCP server and allow you to interact with the Wateroom API through the defined tools.
Use with Claude Desktop
To use this MCP server with Claude Desktop, you do not need to run npx @topotal/waroom-mcp manually, instead add the following to the Claude Desktop configuration file:
MacOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"waroom-mcp": {
"command": "npx",
"args": ["@topotal/waroom-mcp"],
"env": {
"WAROOM_API_KEY": "your-api-key"
}
}
}
}After that, start Claude Desktop as normal. If you are using nodenv or nvm you may need to specify the full path to npx command.
Available Tools
This Model Context Protocol server provides the following Waroom-related tools:
Incident Related
waroom_get_incidents: Get a list of incidents
waroom_get_incident_details: Get details of a specific incident
Postmortem Related
waroom_get_postmortems: Get list of postmortems
debug
First, build the project:
npm install
npm run buildDebugging MCP servers can be difficult because they run over stdio, so for the best debugging experience we highly recommend using MCP Inspector.
You can launch MCP Inspector via npm with the following command:
npx @modelcontextprotocol/inspector "./dist/main.js"Make sure your environment variables are configured properly.
Once launched, the Inspector will show you a URL that you can visit in your browser to start debugging.
Publish
To publish a new version of your package, follow these steps:
Pull the latest code from the main branch
git checkout main git pull origin mainBuild the package
npm run buildPublish to npm
npm publishPush your changes to the remote repository
git push origin main --tags
contribution
Contributions are welcome! Fork the repository and submit pull requests for improvements and bug fixes.
license
This project is licensed under the MIT License, see the LICENSE file for details.
Available Tools
19 toolswaroom_create_incidentC
インシデントを作成します。
Inputs: title (required), severity (required), description (required), service_name (required), +2 more.
waroom_create_incident_action_itemB
特定のインシデントに新しいアクションアイテムを作成します。
Inputs: title (required), incident_uuid (required), status.
waroom_create_postmortemC
ポストモーテムを作成します。
Inputs: blob (required), title (required), incident_uuids (required), status.
waroom_create_service_labelC
特定のサービスに新しいラベルを作成します。
Inputs: name (required), color (required), service_name (required).
waroom_delete_service_labelC
特定のサービスのラベルを削除します。
Inputs: label_uuid (required), service_name (required).
waroom_get_incident_action_itemA
特定のインシデントのアクションアイテム詳細を取得します。
Inputs: incident_uuid (required), action_item_uuid (required).
waroom_get_incident_action_itemsA
特定のインシデントのアクションアイテム一覧を取得します。
Inputs: incident_uuid (required), page, per_page.
waroom_get_postmortemsC
ポストモーテムの一覧を取得します。
Inputs: page, per_page.
waroom_get_postmortem_templateB
ポストモーテムテンプレートを取得します。
Inputs: no named parameters.
waroom_get_runbookB
ランブックの詳細を取得します。namespace で指定します。
Inputs: namespace (required).
waroom_get_runbooksB
ランブックの一覧を取得します。
Inputs: page, per_page.
waroom_get_service_architecture_contextC
特定のサービスのアーキテクチャコンテキストを取得します。
Inputs: service_name (required).
waroom_get_service_labelsC
特定のサービスのラベル一覧を取得します。
Inputs: service_name (required), page, per_page.
waroom_get_servicesC
サービスの一覧を取得します。
Inputs: page, per_page.
waroom_get_usersA
組織のユーザー一覧を取得します。アクションアイテムの担当者指定などに使う nickname を確認できます。
Inputs: page, per_page.
waroom_update_incident_action_itemA
特定のインシデントのアクションアイテムを更新します。タイトル・ステータス(完了・スキップ等)・担当者を変更できます。
Inputs: incident_uuid (required), action_item_uuid (required), title, status, +1 more.
waroom_update_incident_labelsC
インシデントにラベルを付与または更新します。
Inputs: label_uuids (required), incident_uuid (required).
waroom_update_incident_severityC
インシデントの重要度を更新します。
Inputs: severity (required), incident_uuid (required).
waroom_update_runbookC
ランブックを更新します。namespace で対象を指定し、内容(blob)や namespace を変更できます。
Inputs: namespace (required), blob, new_namespace.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 19 tools
Each tool targets a distinct resource and action, spanning incidents, postmortems, services, runbooks, action items, and users. Even similar tools, like incident label updates versus severity updates, are clearly separated.
All tools follow a consistent `waroom_<verb>_<resource>` snake_case pattern. Plural nouns are used for list operations and singular nouns for item-level operations, making the naming predictable.
19 tools is on the heavy side for a single server, though the broad incident-management scope includes service labels, runbooks, postmortems, and action items, which justifies most of them.
Action items have solid CRUD coverage, but incidents lack get/list operations, postmortems lack detail/update/delete operations beyond template retrieval, and runbooks have no create/delete. These are notable gaps in an otherwise broad surface.
Maintenance
Related MCP Connectors
Enable secure connectivity between Sentry issues and debugging data, and LLM clients, using a Model Context Protocol (MCP) server.
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Model Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 100+ accounting systems, HRIS platforms, file storage providers, and more through one integration. More information https://www.apideck.com/mcp-server
The Mercado Pago MCP Server implements the Model Context Protocol to provide AI agents and LLMs with access to Mercado Pago's APIs and tools within compatible development environments. It acts as an intermediary that translates Mercado Pago resources into executable functions (tools) that AI applications can invoke to perform actions and automate flows. The server simplifies integration, enables using documentation to implement or improve code, and optimizes operations through natural language interactions without manual implementations.
Related MCP Servers
- AlicenseAqualityDmaintenanceA Model Context Protocol server that facilitates integration with OpenCTI, allowing users to query and retrieve cyber threat intelligence data via a standardized interface.1643MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that provides a standardized interface for AI models to access, query, and modify content in Notion workspaces.4MIT
- AlicenseDqualityDmaintenanceA Model Context Protocol server that connects to AppSignal, allowing users to fetch, list, and analyze incident information from their AppSignal monitoring.33MIT
- FlicenseNot gradedqualityDmaintenanceA server implementation of the Model Context Protocol (MCP) that provides REST API endpoints for managing and interacting with MCP resources.-