Table of Contents


RabbitMQ supports a variety of plugins. This page contains links to some of our plugins, packaged as .ez files. The links on this page reference plugins built for the latest version of the server, 2.4.1.

The simplest way to install plugins is to download all the required .ez files from this page, drop them in your plugins directory and restart RabbitMQ. The plugins directory location is determined by the RABBITMQ_PLUGINS_DIR environment variable whose default value depends on how you installed RabbitMQ. Some common values are:

Installation methodPlugins directory
Deb / RPM packages /usr/lib/rabbitmq/lib/rabbitmq_server-version/plugins
Windows Typically C:\Program Files\RabbitMQ\rabbitmq_server-version\plugins (depending on where it was installed)
Macports /opt/local/lib/rabbitmq/lib/rabbitmq_server-version/plugins
Generic Unix rabbitmq_server-version/plugins (depending on where it was installed)

Maintained Plugins


A management / monitoring API over HTTP, along with a browser-based UI. For more information, see the page on the management plugin.

To use this plugin the following files are required:

Note: When installing the management plugin on some of the nodes in a cluster, you must install rabbitmq-management-agent on all of the nodes in the cluster. You can install the full management plugin on as many of the nodes as you want.


A gateway for exposing AMQP functionality via the STOMP protocol, as implemented by many clients for various programming languages, and a few other servers besides RabbitMQ.

Please see the documentation and our various blog articles about the adapter for more information on compiling and configuring it.

To use this plugin the following files are required:


An Erlang client for RabbitMQ. This client offers both a networked version that uses standard TCP-based AMQP framing and a direct client that uses native Erlang message passing to a RabbitMQ broker. See the user guide and the README for more information.

This plugin is a dependency of some others, but can also be used standalone (not embedded in the server). Such use is outside the scope of this page.

Building Plugins

You can also build plugins from source. We do not explicitly release source tarballs for plugins, but the repositories can all be found on our Mercurial server. See the plugin development guide for more information on building plugins from source.

Note that plugins tend to be strongly bound to the a certain version of rabbitmq-server. For example, if you are running RabbitMQ 2.4.1, you should check out all plugins with the tag rabbitmq_v2_4_1.


We compile the plugins when we make a release of the server, so in general, each plugin has been compiled against the latest release of the server code (and the plugin's dependencies). We may also from time to time post "known good" binaries; these will be marked with a particular server version with which they are known to work.

Since the default location of the plugins directory is version-specific, installing / upgrading to a new version of the server disables all plugins. That is the safest option since often plugins depend on specific versions of the server. Alternatively, plugins can be retained across upgrades by setting RABBITMQ_PLUGINS_DIR to a location shared by all installed rabbitmq server versions.