Skip to main content
Glama
topotal

Waroom MCP

by topotal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Waroom MCP

No user-submitted related servers found.

    Related Servers

    • OpenCTI MCP Server

      zxzinn
      A
      license
      A
      quality
      C
      maintenance
      A Model Context Protocol server that facilitates integration with OpenCTI, allowing users to query and retrieve cyber threat intelligence data via a standardized interface.
      16
      40
      MIT
    • Cortex MCP by cortexapps

      Cortex MCPofficial

      cortexapps
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that provides natural language access to Cortex API, enabling users to query information about their system's structure and make faster decisions about services, incidents, and team responsibilities.
      8
      MIT

    • MCP REST API Server

      vinaykp
      F
      license
      Not graded
      quality
      D
      maintenance
      A server implementation of the Model Context Protocol (MCP) that provides REST API endpoints for managing and interacting with MCP resources.
      -

    • Incident Triage MCP

      felixkwasisarpong
      A
      license
      C
      quality
      C
      maintenance
      Incident Triage MCP is a Model Context Protocol (MCP) server for incident triage. It provides safe, auditable tools for evidence retrieval, deterministic summaries, ticket workflows, and notifications.
      28
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.2/5.0

    Scored across 19 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count3/5

    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.

    Completeness3/5

    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

    ActivityStale
    ResponsivenessUnresponsive

    Resources