Overview
What is Broker MCP?
Broker MCP is a MCP server for Message Aid that enables managing message brokers — RabbitMQ, Azure Service Bus, and SQS — through the Model Context Protocol. It allows MCP clients to inspect and control broker resources such as queues, topics, and subscriptions.
How to use Broker MCP?
Run the server via Docker, setting the BROKER_URL environment variable to the target broker URL (e.g., rabbitmq://guest:guest@localhost:15672/). The server communicates over STDIO and can be configured in MCP clients like Cursor using a JSON configuration.
Key features of Broker MCP
- Supports RabbitMQ, Azure Service Bus, and SQS brokers.
- Resources for listing queues, topics, and subscriptions.
- Tool to purge queues (RabbitMQ only).
- Configurable operation modes: ReadOnly, MessageAllowed, BrokerAllowed.
- STDIO transport; streamable transport planned.
- Built with .NET and the MCP C# SDK.
Use cases of Broker MCP
- Inspect RabbitMQ queues and topics via MCP tools.
- Purge a RabbitMQ queue from an MCP-enabled client.
- Manage broker resources during development workflows.
- Integrate broker operations into AI-assisted coding environments.
FAQ from Broker MCP
What brokers are currently supported?
RabbitMQ is fully supported. Azure Service Bus and SQS support is planned for most resources and tools.
How do I connect to a broker?
Set the BROKER_URL environment variable with a URL like rabbitmq://guest:guest@localhost:15672/, azure://broker/name, or sqs://localhost/vhost/name.
What does the MCP_MODE configuration do?
MCP_MODE controls the server's permissions: ReadOnly (view only), MessageAllowed (send/receive messages), or BrokerAllowed (manage broker resources). Default is not specified.
Is Broker MCP ready for production?
The server is licensed under BSL 1.1. Some features are planned but not yet implemented for all brokers, so verify support for your broker.
What transport does Broker MCP use?
It uses STDIO transport. Streamable transport is planned, pending support in the MCP C# SDK.
