Thank you to all the people building the future with us.

Read More


RabbitMQ supports a variety of plugins. This page documents the plugins that ship with RabbitMQ 3.7.4.

To enable plugins, use the rabbitmq-plugins tool:

rabbitmq-plugins enable plugin-name

And to disable plugins again, use:

rabbitmq-plugins disable plugin-name

You can see a list of which plugins are enabled with:

rabbitmq-plugins list

The rabbitmq-plugins comand will enable or disable plugins by updating the plugin configuration file. It will then contact the running server to tell it to start or stop plugins as needed. You can use the -n option to specify a different node, or use --offline to only change the file.

For more information on rabbitmq-plugins, consult the manual page.

In addition to the plugins bundled with the server, we also offer binary downloads of plugins which have been contributed by authors in the community. See the community plugins page for more detail on which plugins are available and how to install them.

Supported Plugins

AMQP 1.0 protocol support. This plugin is several years old and is moderately mature. It may have certain limitations with its current architecture but most major AMQP 1.0 features should be in place.
Authentication / authorisation plugin using an external LDAP server.
Authentication / authorisation plugin that uses an external HTTP API.
Authentication mechanism plugin using SASL EXTERNAL to authenticate using TLS (x509) client certificates.
Consistent hash exchange type.
Scalable messaging across WANs and administrative domains.
Shows federation status in the management API and UI. Only of use when using rabbitmq_federation in conjunction with rabbitmq_management. In a heterogenous cluster this should be installed on the same nodes as rabbitmq_management.
A management / monitoring API over HTTP, along with a browser-based UI.
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.
An adapter implementing the MQTT 3.1 protocol.
A plug-in for RabbitMQ that shovels messages from a queue on one broker to an exchange on another broker.
Shows shovel status in the management API and UI. See the plugin README for this plugin. Only of use when using rabbitmq_shovel in conjunction with rabbitmq_management. In a heterogenous cluster this should be installed on the same nodes as rabbitmq_management.
Provides STOMP protocol support in RabbitMQ.
Adds message tracing to the management plugin. Logs messages from the firehose in a couple of formats.
Provides a client x509 certificate trust store.
STOMP-over-WebSockets: a bridge exposing rabbitmq_stomp to web browsers using WebSockets.
MQTT-over-WebSockets: a bridge exposing rabbitmq_mqtt to Web browsers using WebSockets.
Adds some basic examples to rabbitmq_web_stomp: a simple "echo" service and a basic canvas-based collaboration tool.
Adds some basic examples to rabbitmq_web_mqtt: a simple "echo" service and a basic canvas-based collaboration tool.


All plugins below have been discontinued. They don't (or won't) ship with the RabbitMQ distribution and are no longer maintained.

Broker topology visualiser plugin which is itself a plugin to the management plugin. Adds a Visualiser tab to the management web interface, which then flexibly and interactively displays channels, queues and exchanges, and the links between them.

Getting Help and Providing Feedback

If you have questions about the contents of this guide or any other topic related to RabbitMQ, don't hesitate to ask them on the RabbitMQ mailing list.

Documentation feedback is also very welcome on the list. If you'd like to contribute an improvement to the site, its source is available on GitHub.