Skip to main content
Glama
sobue-code

RabbitMQ MCP Server

by sobue-code
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to RabbitMQ 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
      177 npm
      1
      MIT

    • sslwebsites

      jyswee
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for SSL certificate management, enabling agents to issue, renew, revoke, monitor, download, and install certificates, with expiry tracking and webhooks across nine server types.
      20 npm
      -

    • AccelMCP

      t-ogawa-dev
      F
      license
      Not graded
      quality
      B
      maintenance
      An MCP server with HTTP/stdio support, a web admin panel for managing services, capabilities, and user permissions with Bearer token authentication, enabling relay and access control for MCP tools.
      -

    • jakubs-mcp-tools

      Jakub2841
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server for infrastructure discovery and remote management, enabling SSH command execution, file transfer, log tailing, and machine/service inventory with a companion web dashboard.
      2
      -
    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 16 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: connect/status/disconnect manage connection, queue/exchange operations are separate, publish vs publish_to_queue are clearly differentiated by target (exchange vs default exchange), and get_message vs queue_message_count serve different purposes. No two tools appear to do the same thing.

    Naming Consistency4/5

    The naming follows a consistent rabbitmq_<verb>_<noun> pattern for most tools (e.g., list_queues, declare_queue, delete_queue). Minor deviations exist: 'rabbitmq_status' uses a noun instead of a verb phrase, and 'rabbitmq_queue_message_count' is an awkward noun-heavy construction rather than a verb-first name. Overall the pattern is predictable and readable.

    Tool Count4/5

    16 tools is slightly above the typical well-scoped range of 3-15, but the breadth is justified by covering connection management, queue and exchange lifecycle, bindings, publishing, and message retrieval. It does not feel bloated or redundant, given the full RabbitMQ management surface.

    Completeness4/5

    The tool surface covers core RabbitMQ operations: connection handling, queue/exchange CRUD, bindings, publishing, and message inspection. Minor gaps exist, such as no list_bindings or get_exchange tool, but agents can still perform most common workflows. No severe missing operations that would cause failures.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources