Skip to main content
Glama
sansong089

RabbitMQ MCP Server

by sansong089
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
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

    • Rocket.Chat MCP Server

      elieworkspace
      F
      license
      Not graded
      quality
      F
      maintenance
      Enables interaction with Rocket.Chat instances through MCP protocol. Allows users to manage chat operations and integrate with Rocket.Chat servers using natural language commands.
      6
      -

    • RabbitMQ MCP Server

      sobue-code
      A
      license
      B
      quality
      D
      maintenance
      MCP server for RabbitMQ with full SSL/CA certificate support, enabling queue, exchange, binding, and message management operations.
      16
      Apache 2.0

    • RabbitMQ MCP Server

      amazon-mq
      A
      license
      B
      quality
      A
      maintenance
      Enables AI agents to manage RabbitMQ message brokers through admin APIs, supporting multiple brokers, OAuth authentication, and mutative tools.
      39
      91 PyPI
      41
      Apache 2.0

    • ecp-mcp-server

      EpicLabs23
      A
      license
      C
      quality
      C
      maintenance
      Enables conversational management of hosting account resources such as apps, domains, databases, files, PHP, SSL, and more through MCP-compatible clients.
      194
      147 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

    C2.9/5.0

    Scored across 20 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action (e.g., list_vhosts vs. create_vhost vs. delete_vhost, publish_message vs. consume_message). There is no meaningful overlap; an agent can reliably select the intended operation.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern (list_*, create_*, delete_*, get_*, publish_*, consume_*). The convention is predictable throughout, with no mixing of styles or vague verbs.

    Tool Count4/5

    20 tools is slightly above the typical 3–15 sweet spot, but the set covers distinct RabbitMQ resources without obvious redundancy. The count is reasonable for a management server spanning vhosts, users, queues, exchanges, bindings, and messages.

    Completeness3/5

    Core create/list/delete operations exist for vhosts, users, queues, exchanges, and bindings, and exchange has a get operation, but many resources lack detailed get or update tools (users, queues, vhosts, bindings). Additional gaps include queue purge, message ack/reject, and connection management, though agents can partially work around these via list operations.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources