Loading...
RabbitMQ management API offers extensive control over message queues, exchanges, and users, but lacks sandboxing and requires careful access control to prevent misuse.
Boost this tool
Subscribe to listing upgrades or segmented pushes.
RabbitMQ management API offers extensive control over message queues, exchanges, and users, but lacks sandboxing and requires careful access control to prevent misuse.
The RabbitMQ management API provides powerful administrative capabilities but poses significant risks if not properly secured. It's safe when access is strictly controlled using RBAC and TLS is enabled. It's risky when default credentials are used, RBAC is overly permissive, or the API is exposed to untrusted networks.
Performance depends on the size of the RabbitMQ cluster and the complexity of the API calls. Rate limiting may be necessary to prevent overload.
There are no direct costs associated with the management API itself, but the underlying RabbitMQ infrastructure incurs resource costs.
npx -y{
"mcpServers": {
"rabbitmq": {
"command": "uvx",
"args": [
"mcp-server-rabbitmq@latest",
"--rabbitmq-host",
"<hostname ex. test.rabbit.com, localhost>",
"--port",
"<port number ex. 5672>",
"--username",
"<rabbitmq username>",
"--password",
"<rabbitmq password>",
"--use-tls",
"<true if uses amqps, false otherwise>"
]
}
}
}list_queuesLists all queues in the RabbitMQ broker.
Read-only operation, no side effects.
create_exchangeCreates a new exchange in the RabbitMQ broker.
Creates a new resource, but doesn't immediately impact existing operations.
delete_queueDeletes a queue from the RabbitMQ broker.
Destructive operation, can lead to data loss.
set_permissionsSets permissions for a user on a virtual host.
Modifies access control, potentially granting unintended privileges.
API Key
amqp.readamqp.writeamqp.configureadministratormonitoringThe RabbitMQ management API provides powerful administrative capabilities but poses significant risks if not properly secured. It's safe when access is strictly controlled using RBAC and TLS is enabled. It's risky when default credentials are used, RBAC is overly permissive, or the API is exposed to untrusted networks.
Autonomy is entirely dependent on the configured permissions. Incorrectly configured permissions can lead to unintended consequences.
Production Tip
Implement robust error handling and monitoring to detect and respond to failures quickly.
The management API supports username/password authentication and potentially other methods depending on the RabbitMQ configuration.
Use strong passwords, enable TLS encryption, and configure RBAC to restrict access to only necessary resources.
Yes, the API provides endpoints for creating, deleting, and managing queues.
The API provides endpoints for retrieving queue statistics, including message counts.
No, the API does not provide a mechanism for recovering deleted messages. Implement message persistence and backups for data recovery.
By default, messages in the queue will be discarded when the queue is deleted. Configure message persistence to prevent data loss.
You need to configure TLS within RabbitMQ itself, typically by providing certificates and keys in the RabbitMQ configuration file.