RabbitMQ MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| rabbitmq_broker_initialize_connectionC | Connect to a new RabbitMQ broker which authentication strategy is SIMPLE. |
| rabbitmq_broker_initialize_connection_with_oauthB | Connect to a new RabbitMQ broker using OAuth. |
| rabbitmq_broker_selectA | Switch the active broker by alias. All subsequent tool calls will target this broker. |
| rabbitmq_broker_list_registered_brokersA | List all registered broker connections and which is active. |
| rabbitmq_broker_get_guidelineA | Get the general best practices for deploying RabbitMQ on Amazon MQ. |
| rabbitmq_broker_get_skillC | Get a workflow recipe. Available: pre_flight_migration_check, migrate_definitions, setup_federation, queue_metrics_analysis, node_resource_analysis, export_topology_graph, trace_message_route, find_orphaned_queues, find_unbound_exchanges, trace_dead_letter_chain, inspect_dead_letters, dlq_summary, broker_recommendations, queue_health_assessment, resource_headroom_check, policy_conflict_detection |
| rabbitmq_broker_list_queuesB | List all the queues in the broker. |
| rabbitmq_broker_list_exchangesB | List all the exchanges in the broker. |
| rabbitmq_broker_list_vhostsA | List all the virtual hosts (vhosts) in the broker. |
| rabbitmq_broker_get_queue_infoC | Get detailed information about a specific queue. |
| rabbitmq_broker_get_exchange_infoC | Get detailed information about a specific exchange. |
| rabbitmq_broker_list_shovelsB | Get detailed information about shovels in the RabbitMQ broker. |
| rabbitmq_broker_get_shovel_infoA | Get detailed information about specific shovel by name that is in a selected virtual host (vhost) in the RabbitMQ broker. |
| rabbitmq_broker_get_cluster_nodes_infoB | Get the list of nodes and their info in the cluster. |
| rabbitmq_broker_list_connectionsB | List all connections on the RabbitMQ broker. |
| rabbitmq_broker_list_consumersA | List all consumers on the RabbitMQ broker. |
| rabbitmq_broker_list_usersB | List all users on the RabbitMQ broker. |
| rabbitmq_broker_is_in_alarmB | Check if the RabbitMQ broker is in alarm. |
| rabbitmq_broker_is_quorum_criticalA | Check if there are quorum queues with minimum online quorum. |
| rabbitmq_broker_get_broker_definitionA | Get the RabbitMQ definitions: exchanges, queues, bindings, users, virtual hosts, permissions, topic permissions, and parameters. Everything apart from messages. |
| rabbitmq_broker_get_bindingsA | Get bindings, optionally filtered by queue or exchange. If neither is specified, returns all bindings in the vhost. |
| rabbitmq_broker_get_node_informationB | Get detailed information about a specific node in the cluster including memory, disk, uptime, and runtime details. |
| rabbitmq_broker_list_policiesC | List all policies in a virtual host. |
| rabbitmq_broker_get_policyC | Get a specific policy by name. |
| rabbitmq_broker_get_messagesA | Peek at messages in a queue without consuming them. Messages are requeued by default. |
| rabbitmq_broker_list_channelsA | List all open channels on the broker. |
| rabbitmq_broker_get_permissionsC | Get permissions for a user in a virtual host. |
| rabbitmq_broker_compare_definitionsA | Compare definitions between two connected brokers. Returns missing/extra items per section (queues, exchanges, bindings, policies, vhosts). |
| rabbitmq_broker_check_migration_readinessB | Pre-flight check for blue-green migration. Verifies both brokers connected, no alarms, and topology match. |
| rabbitmq_broker_check_local_alarmsA | Check for local alarms on the active broker. |
| rabbitmq_broker_check_certificate_expirationB | Check if any TLS certificates expire within the given timeframe. |
| rabbitmq_broker_check_protocol_listenerC | Check if a protocol listener is active. |
| rabbitmq_broker_check_virtual_hostsA | Check health of all virtual hosts on the active broker. |
| rabbitmq_broker_list_feature_flagsA | List all feature flags and their status. |
| rabbitmq_broker_list_deprecated_featuresA | List deprecated features currently in use. Useful for upgrade planning. |
| rabbitmq_broker_whoamiA | Get the current authenticated user on the active broker. |
| rabbitmq_broker_get_overviewC | Broker version, totals, and rates. |
| rabbitmq_broker_find_queues_by_thresholdB | Find queues exceeding threshold criteria. |
| rabbitmq_broker_get_connection_churnB | Connection and channel churn rates. |
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 39 tools
Most tools have distinct purposes due to descriptive naming (e.g., check vs list vs get). However, a few pairs like 'check_local_alarms' and 'is_in_alarm' are very similar, and the sheer number of tools increases the chance of misselection. Overall, an agent can generally distinguish them.
All tools follow the consistent 'rabbitmq_broker_verb_noun' pattern in snake_case. Verbs like check, list, get, is, find, compare, initialize are used uniformly. Multi-word nouns are consistently hyphenated or underscore-separated. No mixed conventions.
39 tools exceed the 'too many' threshold of 25 for typical MCP servers. While the domain is broad, the toolset could be consolidated (e.g., combining multiple check tools into parameterized ones). This high count burdens discovery and selection.
For a monitoring/diagnostics and migration assist tool, the coverage is strong: health checks, listings, details, comparisons, guidelines, and skills. Notable read-only bias means no create/update/delete tools, but that appears intentional. Minor gaps like missing per-exchange message rates don't hinder core workflows.