Skip to main content
Glama
bluematador

blue-matador-mcp-server

Official
by bluematador
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to blue-matador-mcp-server

No user-submitted related servers found.

    Related Servers

    • dimetrics-mcp-server

      fellnerd
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables natural language management of apps, services, resources, attributes, and data via the Dimetrics API with full CRUD operations and advanced filtering.
      -

    • vibeMK

      chexma
      A
      license
      C
      quality
      D
      maintenance
      Enables complete management of CheckMK monitoring environments through natural language, including live monitoring, downtime scheduling, problem management, and configuration.
      115
      17
      GPL 3.0

    • Netris MCP Server

      iamjarvs
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables managing Netris network fabric through natural language, including VPCs, BGP sessions, load balancers, NAT rules, IPAM, and other network operations.
      -
    • zsvirt-mcp-server by ZSvirt

      zsvirt-mcp-serverofficial

      ZSvirt
      A
      license
      A
      quality
      B
      maintenance
      Enables natural language discovery, inspection, and execution of ZStack's 2000+ cloud management APIs, plus searching and retrieving monitoring metrics, with read-only safety controls and multi-tenant authentication support.
      6
      4
      MIT
    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.3/5.0

    Scored across 41 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action (e.g., create_aws_integration vs create_azure_integration, different notification types). Even similar tools like mute_monitors_by_service and mute_resources_by_wildcard have clear differentiation via description.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern in snake_case (e.g., 'list_integrations', 'create_pagerduty_notification', 'disable_integration'). No mixing of styles or unexpected abbreviations.

    Tool Count4/5

    With 41 tools, the count is high but justified by the breadth of functionality: multiple integration types, notification channels, mute rules, events, and user management. Slightly above the ideal 3-15 range but not excessive for a monitoring platform.

    Completeness4/5

    The surface covers CRUD operations for integrations and notifications, event queries, mute rules, users, and projects. Minor gaps exist: no update for mute rules, no delete for users, and no direct tools for managing monitor definitions. Overall, core workflows are supported.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources