ibm-mq-mcp
Related Servers
Alternatives to ibm-mq-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables LLMs to declare and manage RabbitMQ AMQP topologies, publish and consume messages, diagnose backlogs, and monitor cluster and connection health through MCP.2052 PyPIApache 2.0
- FlicenseNot gradedqualityCmaintenanceBridges LLMs to IBM QRadar SIEM via 4 intelligent MCP tools covering 728 REST API endpoints, enabling natural language queries for offenses, assets, rules, and more.-

IBM Business Automationofficial
AlicenseNot gradedqualityCmaintenanceEnables AI agents to integrate with IBM Business Automation Workflow by exposing workflow REST services as MCP tools, allowing natural language interaction with business automation capabilities.11Apache 2.0- 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
- AlicenseBqualityCmaintenanceEnables MCP-compatible LLM clients to interact with IBM Planning Analytics/TM1 models through callable tools, supporting read operations like inspecting cubes, dimensions, and MDX queries, plus write/model-building operations in read/write mode.13MIT

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
TDQS
Scored across 15 tools
Most tools cleanly separate list/get operations for each resource and message actions are clearly distinct. The main overlap is run_mqsc vs run_mqsc_json, which both execute MQSC but differ by output format and argument style; their descriptions mitigate but do not eliminate potential misselection.
All tools use consistent snake_case verb_noun naming: list_* for enumerations, get_* for single-object retrievals, and action_message for messaging operations. The run_mqsc / run_mqsc_json pair follows a clear pattern with a format suffix.
15 tools form a well-scoped administration and messaging surface for IBM MQ: resource queries, message operations, and a generic MQSC escape hatch. Every tool serves a plausible purpose without bloat.
The domain is broadly covered: queue managers, queues, channels, subscriptions, topics, messages, and installation info all have query tools, with message put/get/publish/browse operations present. Minor gaps exist—no dedicated get_subscription or get_topic, no direct create/update/delete tools, and browse_message lacks pagination—but run_mqsc fills most gaps.