ballerina-activemq-mcp-server
Related Servers
Alternatives to ballerina-activemq-mcp-server
No user-submitted related servers found.
Related Servers
- FlicenseAqualityFmaintenanceEnables AI assistants to set up, run, and manage Ballerina + Salesforce integrations inside a WSO2 Integrator workspace, providing 18 tools for OAuth2 token acquisition, project scaffolding, building, deploying, and stopping the integration service.18-
- AlicenseCqualityCmaintenanceEnables AI assistants to manage ActiveMQ message brokers through MCP tools, supporting queue and topic operations, dynamic connection management, message browsing, and health monitoring.2214 npm1MIT

JMSToolBox MCP Serverofficial
AlicenseNot gradedqualityAmaintenanceEnables AI assistants to connect to JMS brokers such as IBM MQ, ActiveMQ, Artemis, RabbitMQ, TIBCO, Solace, and WebLogic, browse queues non-destructively, inspect messages and queue depth, and optionally send or consume messages when read-only safeguards are disabled. It auto-discovers JMSToolBox configurations and loads broker client drivers dynamically.332 npm1Apache 2.0- FlicenseNot gradedqualityDmaintenanceAutomates the initialization of Java 21/Spring Boot microservices with Docker Compose, generating complete project archetypes for Seguros Bolivar.-
- AlicenseAqualityCmaintenanceAn MCP server that lets an AI agent work with an ActiveMQ Artemis broker.84 npm1MIT
- FlicenseAqualityBmaintenanceEnables LLM clients to interact with IBM MQ by exposing management and messaging REST APIs as 15 MCP tools, covering queue manager queries, MQSC commands, object inspection, and message send/receive operations.15-
TDQS
Scored across 9 tools
Each tool targets a distinct lifecycle stage or resource type: broker validation, project scaffolding, config writing, queue/topic/listener additions, ack mode editing, build, and deploy. The only similar pair (add_queue vs add_topic) is clearly differentiated by destination type (point-to-point vs pub/sub).
All tool names follow the consistent 'mq_verb_noun' pattern with snake_case throughout. Examples include mq_validate_broker, mq_scaffold_project, mq_add_queue, mq_set_ack_mode, and mq_build_project. This uniform convention makes tool discovery and selection highly predictable.
With 9 tools, the server is well-scoped for its purpose of managing an ActiveMQ Ballerina project lifecycle. The count is neither minimal (which would be vague) nor overwhelming, and each tool serves a clear, necessary function from validation through deployment.
The toolset covers the core lifecycle well: validate, scaffold, add components, configure, build, and deploy. Minor gaps exist such as the lack of a remove/teardown tool or a direct JMS message roundtrip test, but these are not critical for the primary scaffolding workflow and can be worked around via the generated code.