IBM MQ MCP Server

An MCP server for safely inspecting and operating multiple IBM MQ environments.

Status

Bootstrap intent accepted. The Go module skeleton and minimal MCP server (no MQ tools yet) start at FND-001. License and OSS maturity posture are recorded in ADR-0009.

task test && task build
task run   # stdio MCP server (no ops HTTP by default)

# Optional ops listener (health, readiness, metrics)
IBM_MQ_MCP_OPS_ADDR=:9090 task run

Operational endpoints (/healthz, /readyz, /metrics) bind only when --ops-addr or IBM_MQ_MCP_OPS_ADDR is set. Optional Streamable HTTP MCP requires --remote-addr plus --remote-auth-token-ref (ADR-0006). See AGENTS.md.

Sources of truth:

• Bootstrap proposal
• Roadmap
• Architecture ADRs
• Design questions

Intended outcomes

• Connect to multiple queue managers through named connection profiles.
• Enforce least-privilege capabilities independently for every profile.
• Offer safe, typed MCP tools for common IBM MQ operations.
• Work with queue managers managed by MKurator, the IBM MQ Operator, or neither.
• Return concise, schema-backed results with explicit pagination and truncation.
• Ship with production-grade tests, documentation, observability, and releases.

Contributing

See CONTRIBUTING.md, CODE_OF_CONDUCT.md, and GOVERNANCE.md. Security reports: SECURITY.md. Help channels: SUPPORT.md.

License

MIT © 2026 Konrad Heimel