Verified

Ibm Mq MCP Server

IBM MQ queue manager operations via typed MCP tools and connection profiles.

Data last scanned today · Reviewed today

43★ 1GoMIT

Overview

This Go-based MCP server provides an interface for inspecting and managing IBM MQ environments. It allows users to define multiple named connection profiles, enabling interaction with queue managers regardless of whether they are managed by the IBM MQ Operator, MKurator, or other setups. The project is in early development stages, focusing on a schema-backed approach to MQ operations. It supports configurable operational endpoints for health monitoring and metrics, along with optional streamable HTTP transport for remote connectivity.

Our verdict

This project holds a high-risk security score of 33/100. It is a community-maintained tool by a single contributor and lacks official vendor oversight or an editorial security review. Because authentication methods and read-only mode safety have not been independently audited, users should exercise significant caution before deploying this in environments where data integrity or access controls are critical.

Zero direct dependencies reduces the supply-chain surface area.
Project includes a documented security report and governance process.
Supports configurable ops endpoints like health and metrics.
Released under the MIT license.

Community-maintained repository lacks official IBM vendor support.
High-risk security score due to lack of independent audit.
Single-contributor project increases long-term bus-factor risk.
Read-only mode and authentication mechanisms currently lack verification.

Compatibility

Client	Local	Docker	Remote	Read-only
Claude Desktop
Cursor
VS Code
Windsurf
ChatGPT

Frequently asked questions

›How can I enable operational monitoring endpoints?

You can expose operational endpoints like healthz, readyz, and metrics by setting the IBM_MQ_MCP_OPS_ADDR environment variable or using the --ops-addr command line flag.

›What is required to use the optional Streamable HTTP transport?

To use the HTTP MCP transport, you must configure both the --remote-addr and --remote-auth-token-ref flags.