RabbitMQ MCP Server
Related Servers
Alternatives to RabbitMQ MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceAn MCP server for RabbitMQ that exposes the RabbitMQ HTTP API as tools, enabling natural language interaction with RabbitMQ management.100339 npm1MIT
- FlicenseNot gradedqualityFmaintenanceEnables interaction with Rocket.Chat instances through MCP protocol. Allows users to manage chat operations and integrate with Rocket.Chat servers using natural language commands.6-
- AlicenseBqualityDmaintenanceMCP server for RabbitMQ with full SSL/CA certificate support, enabling queue, exchange, binding, and message management operations.16Apache 2.0
- AlicenseBqualityAmaintenanceEnables AI agents to manage RabbitMQ message brokers through admin APIs, supporting multiple brokers, OAuth authentication, and mutative tools.39151 PyPI42Apache 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
- AlicenseNot gradedqualityCmaintenanceEnables users to connect to and manage various Cloudflare services such as Workers, observability, DNS analytics, and more through natural language interactions via MCP clients.Apache 2.0
TDQS
Scored across 20 tools
Each tool targets a distinct resource and action (e.g., list_vhosts vs. create_vhost vs. delete_vhost, publish_message vs. consume_message). There is no meaningful overlap; an agent can reliably select the intended operation.
All tool names follow a consistent snake_case verb_noun pattern (list_*, create_*, delete_*, get_*, publish_*, consume_*). The convention is predictable throughout, with no mixing of styles or vague verbs.
20 tools is slightly above the typical 3–15 sweet spot, but the set covers distinct RabbitMQ resources without obvious redundancy. The count is reasonable for a management server spanning vhosts, users, queues, exchanges, bindings, and messages.
Core create/list/delete operations exist for vhosts, users, queues, exchanges, and bindings, and exchange has a get operation, but many resources lack detailed get or update tools (users, queues, vhosts, bindings). Additional gaps include queue purge, message ack/reject, and connection management, though agents can partially work around these via list operations.