RabbitMQ MCP Server
Related Servers
Alternatives to RabbitMQ MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables LLMs to declare and manage RabbitMQ AMQP topologies, publish and consume messages, diagnose backlogs, and monitor cluster and connection health through MCP.2060 PyPIApache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables LLM agents to manage RabbitMQ queues, exchanges, and shovels via MCP tools, with restricted mode for production environments.Apache 2.0
- AlicenseBqualityDmaintenanceAn MCP server for RabbitMQ that exposes the RabbitMQ HTTP API as tools, enabling natural language interaction with RabbitMQ management.100166 npm1MIT
- FlicenseCqualityDmaintenanceEnables management of RabbitMQ clusters, queues, exchanges, bindings, users, and messages through natural language in chat interfaces, using the MCP protocol.201-
- AlicenseNot gradedqualityBmaintenanceEnables AI clients to turn message contracts into typed tools for publishing and requesting RabbitMQ messages, inspecting queues and faults, and safely republishing or parking failed messages. It also supports answering service requests in responder mode and enforcing roles, rate limits, and audits for teams.MIT
- AlicenseCqualityDmaintenanceEnables AI assistants to manage ActiveMQ message brokers through MCP tools, supporting queue and topic operations, dynamic connection management, message browsing, and health monitoring.2219 npm1MIT
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.