Skip to main content
Glama
StevePic95

RabbitMQ MassTransit MCP Server

by StevePic95
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to RabbitMQ MassTransit MCP Server

No user-submitted related servers found.

    Related Servers

    • rabbitmq-mcp

      kmitchell
      A
      license
      B
      quality
      D
      maintenance
      An MCP server for RabbitMQ that exposes the RabbitMQ HTTP API as tools, enabling natural language interaction with RabbitMQ management.
      100
      144 npm
      1
      MIT

    • ticket-forge

      SanjoyDat1
      -
      license
      Not graded
      quality
      Not graded
      maintenance
      MCP server that parses stack traces and logs to generate deduplicated issue drafts with severity, repro steps, and owner guesses.
      -

    • automation-health-mcp

      chainwright
      A
      license
      A
      quality
      C
      maintenance
      An MCP server for auditing automation health, finding failures, stale logs, and non-functional endpoints that report success while quietly failing.
      7
      MIT

    • log-collector

      bonsai
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for collecting and analyzing CLI/web server error logs. Enables watching log files/directories, parsing common error patterns, and querying/analyzing logs through natural language.
      3 npm
      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

    A3.9/5.0

    Scored across 13 tools

    Disambiguation5/5

    Each tool targets a distinct RabbitMQ resource or action: overview, queues, exchanges, bindings, messages, connections, consumers, error/skipped queues, and health. Even the two peek tools are clearly separated by normal vs. error queues with different decoding purposes.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using snake_case: get_*, list_*, peek_*. There is no mixing of verb styles or casing conventions.

    Tool Count5/5

    13 tools is well within the ideal range for a monitoring-oriented server. Each tool earns its place by covering a distinct observability or troubleshooting need without redundancy.

    Completeness4/5

    The observability workflow is well covered: discover queues/exchanges/bindings, inspect consumers/connections, peek messages, and surface MassTransit error/skipped queues with health findings. Minor management gaps like queue/exchange creation or purge/replay operations exist, but they appear to be outside the intended read-only monitoring scope.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources