JMSToolBox MCP Server

Model Context Protocol (MCP) server for JMS messaging brokers, built with Java 17 and the official Java MCP SDK (io.modelcontextprotocol.sdk:mcp-core), packaged as a universal cross-platform CLI tool via npm.

Supports all JMS brokers supported by JMSToolBox (IBM MQ, ActiveMQ, Artemis, RabbitMQ, TIBCO EMS, Solace, Oracle WebLogic, SonicMQ, etc.) by directly leveraging JMSToolBox's configuration and dynamic JAR driver loading.

🌟 Key Features

• Universal JMS Compatibility: Loads broker client JARs on-demand using dedicated URLClassLoaders, eliminating native C client dependencies.

• Auto-Discovery across Platforms:

  • Auto-detects JMSToolBox installation directory on Windows, macOS, and Linux to locate bundled vendor driver JARs.

  • Auto-detects JMSToolBox configuration files from standard locations across operating systems (~/.jtb/JMSToolBox/config.xml, APPDATA, Application Support, XDG_CONFIG_HOME).

• Native Password Decryption: Decrypts encrypted passwords stored in JMSToolBox config.xml directly.

• Safe Queue Browsing: Non-destructive queue inspection with complete headers, properties, and message payloads.

• Safety Safeguards: Destructive tools (send_message, consume_message) are blocked by default unless READ_ONLY=false is set.

• NPM Package & npx Support: Can be installed globally via npm or run directly with Node.js.

Related MCP server: RabbitMQ MCP Server

🛠 Available Tools

📦 Installation & Packaging

Method 1: Global NPM Install (Recommended for Local Dev)

Run the automated build & install script:

npm run publish:local

This builds the fat JAR using Maven, packages the npm tarball, and installs jmstoolbox-mcp globally.

Method 2: Manual Maven Build

mvn clean package

Generates target/jmstoolbox-mcp.jar.

⚙️ MCP Configuration

Add to your .kiro/settings/mcp.json or Claude Desktop configuration:

Option A: Using NPM binary (if installed globally)

{
  "mcpServers": {
    "jmstoolbox": {
      "command": "npx",
      "args": ["-y", "jmstoolbox-mcp"],
      "env": {
        "READ_ONLY": "true"
      },
      "disabled": false,
      "autoApprove": [
        "list_connections",
        "connect",
        "disconnect",
        "get_active_connections",
        "browse_messages",
        "get_queue_depth"
      ]
    }
  }
}

Option B: Using direct launcher script

{
  "mcpServers": {
    "jmstoolbox": {
      "command": "F:\\Documents\\Library\\AI\\jmstoolbox-mcp\\jmstoolbox-mcp.cmd",
      "args": [],
      "env": {
        "READ_ONLY": "true"
      },
      "disabled": false,
      "autoApprove": [
        "list_connections",
        "connect",
        "disconnect",
        "get_active_connections",
        "browse_messages",
        "get_queue_depth"
      ]
    }
  }
}

🔧 Environment Variables