Skip to main content
Glama
atengk

mcp-server-rabbitmq

by atengk

Related Servers

Alternatives to mcp-server-rabbitmq

No user-submitted related servers found.

    Related Servers

    • 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
    • A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to manage RabbitMQ message brokers through admin APIs, supporting multiple brokers, OAuth authentication, and mutative tools.
      39
      434 PyPI
      42
      Apache 2.0
    • F
      license
      A
      quality
      B
      maintenance
      Enables LLM clients to interact with IBM MQ by exposing management and messaging REST APIs as 15 MCP tools, covering queue manager queries, MQSC commands, object inspection, and message send/receive operations.
      15
      -
    • A
      license
      C
      quality
      C
      maintenance
      Enables AI assistants to manage ActiveMQ message brokers through MCP tools, supporting queue and topic operations, dynamic connection management, message browsing, and health monitoring.
      22
      14 npm
      1
      MIT

    TDQS

    A3.6/5.0

    Scored across 20 tools

    Disambiguation3/5

    Most tools are clearly distinct by resource and action, but rabbitmq_list_connections and rabbitmq_list_configured_brokers are explicitly aliases of the same operation, creating a direct duplication. Additionally, rabbitmq_peek_messages and rabbitmq_get_messages overlap in purpose, though their descriptions help differentiate them.

    Naming Consistency5/5

    All 20 tools follow a consistent rabbitmq_verb_noun snake_case pattern with no deviations. The naming is entirely predictable and easy to parse.

    Tool Count4/5

    20 tools is on the high side but still reasonable for a full RabbitMQ broker management surface covering queues, exchanges, bindings, publishing, and diagnostics. One tool (the alias) is redundant, but the set as a whole is well-scoped.

    Completeness4/5

    The surface covers core CRUD for queues and exchanges, binding management, message publish/peek/get, and diagnostic operations. Minor gaps exist, such as no explicit get-exchange details or consumer management tools, but essential workflows are well covered.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive