Loading...
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.
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.