RabbitMQ MassTransit MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RABBITMQ_SSL | No | Use HTTPS for Management API | false |
| RABBITMQ_HOST | Yes | RabbitMQ Management API hostname | |
| RABBITMQ_PORT | No | Management API port | 15672 |
| RABBITMQ_VHOST | No | Default virtual host | / |
| RABBITMQ_PASSWORD | Yes | Authentication password | |
| RABBITMQ_USERNAME | Yes | Authentication username | |
| ALLOW_MUTATIVE_TOOLS | No | Enable mutative tools (purge, delete, publish, republish, move) | false |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_overviewA | Get RabbitMQ cluster overview: queue totals, connection counts, message rates, and version info |
| list_queuesA | List queues with message depth, consumer count, and rates. Filter by vhost and name pattern. |
| get_queueA | Get detailed stats for a specific queue: depth, rates, consumers, memory, policy, arguments. |
| list_exchangesA | List exchanges with type and binding info. Filter by vhost, name pattern, or type. |
| get_exchangeB | Get exchange details and its bindings (both source and destination). |
| list_bindingsA | List bindings for a specific queue or exchange. |
| peek_messagesA | Browse messages in a queue without consuming them (non-destructive). Parses MassTransit envelopes when detected. |
| list_connectionsA | List active RabbitMQ connections with client info, state, and channel count. |
| list_consumersA | List active consumers with their queue assignments, prefetch, and connection info. |
| list_error_queuesB | Find all MassTransit _error queues with message counts. Helps identify services with unprocessed failures. |
| list_skipped_queuesA | Find all MassTransit _skipped queues with message counts. Skipped messages indicate routing or serialization issues. |
| peek_errorsA | Browse error queue messages with parsed MassTransit fault details: exception type, message, stack trace, original payload, and source host. |
| get_queue_healthA | Quick health check: find queues with no consumers, growing depth, or high error counts. Identifies potential issues. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 13 tools
Each tool targets a distinct RabbitMQ resource or action: overview, queues, exchanges, bindings, messages, connections, consumers, error/skipped queues, and health. Even the two peek tools are clearly separated by normal vs. error queues with different decoding purposes.
All tool names follow a consistent verb_noun pattern using snake_case: get_*, list_*, peek_*. There is no mixing of verb styles or casing conventions.
13 tools is well within the ideal range for a monitoring-oriented server. Each tool earns its place by covering a distinct observability or troubleshooting need without redundancy.
The observability workflow is well covered: discover queues/exchanges/bindings, inspect consumers/connections, peek messages, and surface MassTransit error/skipped queues with health findings. Minor management gaps like queue/exchange creation or purge/replay operations exist, but they appear to be outside the intended read-only monitoring scope.