Waroom MCP Server

Waroom mcp mcp server lets Claude, Cursor and other MCP clients work with Waroom MCP directly. Waroom MCP Server - Access Waroom API through Model Context Protocol.

What Waroom MCP does

このプロジェクトは、Waroom APIとインタラクションするためのModel Context Protocol (MCP) サーバーです。標準化されたプロトコルを使用して、Waroomから様々な情報を取得することができます。

Tools it exposes

Once connected, the assistant can call these 14 tools directly:

• waroom_create_incident — インシデントの作成（サービス名、タイトル、重要度など指定）
• waroom_get_incidents — ページネーション対応のインシデント一覧
• waroom_get_incident_details — UUID による個別インシデント詳細
• waroom_update_incident_severity — インシデント重要度の更新
• waroom_update_incident_status — インシデントステータスの更新
• waroom_create_incident_metrics — インシデントメトリクスの作成（TTD/TTA/TTI/TTF/TTR更新）
• waroom_update_incident_labels — インシデントにラベルを付与または更新
• waroom_get_postmortems — ページネーション対応のポストモーテム一覧
• waroom_create_postmortem — ポストモーテムの作成
• waroom_get_postmortem_template — ポストモーテムテンプレート取得
• waroom_get_services — サービス一覧取得
• waroom_get_service_architecture_context — 特定のサービスのアーキテクチャコンテキスト取得
• waroom_update_service_architecture_context — 特定のサービスのアーキテクチャコンテキスト更新
• waroom_get_service_labels — 特定のサービスのラベル一覧を取得

Installing the waroom mcp mcp server

The server is distributed via npm as @topotal/waroom-mcp, so most clients can run it without a manual build step. Add it to your MCP client's configuration and restart the client to pick it up — the copy-paste configs for Claude Desktop, Claude Code and Cursor are on this page.

Configuration

Before the server will start you need to supply one environment variable: WAROOM_API_KEY. Keep credentials in your client's env block or a secrets manager rather than committing them.

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. Waroom MCP sits in that group, and the shape of its toolset — waroom_create_incident, waroom_get_incidents, waroom_get_incident_details among others — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

• This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
• It will not start until its required credentials are present, so set those before wondering why the tools never appear.
• With 14 tools exposed, expect a noticeable bump in prompt size — disable it in projects that never use Waroom MCP.
• Maintained by topotal.
• MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the waroom mcp mcp server actually does with your data.
• Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.