Troubleshooting¶
Server won't start¶
| Symptom | Likely cause | Action |
|---|---|---|
ops listener failed / exit code 1 |
Ops address in use or invalid | Change --ops-addr / IBM_MQ_MCP_OPS_ADDR; check bind permissions |
remote MCP configuration failed |
Remote addr without auth token ref | Set --remote-auth-token-ref / IBM_MQ_MCP_REMOTE_AUTH_TOKEN_REF |
remote MCP listener failed |
Remote address in use or invalid | Change --remote-addr / IBM_MQ_MCP_REMOTE_ADDR |
| MCP host sees no tools | Expected in bootstrap | No MQ tools until INS/MSG/ADM stories land — see Tool reference |
task check fails |
Local gate drift | Run failing subtask (task lint, task test:race, …) — CI gates |
Ops probes¶
| Symptom | Check |
|---|---|
/healthz returns 503 |
Process marked unhealthy in runtime state — inspect stderr logs |
/readyz returns 503 |
Bootstrap config invalid (future profiles) or MCP transport not serving |
Connection refused on :9090 |
Ops HTTP not enabled — set --ops-addr or IBM_MQ_MCP_OPS_ADDR |
| Metrics empty | No tool traffic yet; profile label _none until profiles exist |
Probes intentionally do not ping queue managers. Use the
check_profile_connectivity MCP tool (requires profile inspect) for
side-effect-free mqweb reachability, identity match, and latency. Ops probes
remain catalog-only for readiness.
IBM MQ / mqweb¶
explain_mq_reason_code— offline bundled reference; unknown codes return a generic answer with an IBM documentation link (NOTICE).check_profile_connectivity— read-only queue manager status probe; failures report typed causes (dns,tls,authentication,authorization,timeout,unreachable) without leaking credentials.- Verify mqweb is installed, reachable, and authorized for the profile credential.
- Consult the version support matrix — certified combinations are not yet recorded.
MCP client integration¶
- Use stdio transport pointing at
ibm-mq-mcportask run. - Remote Streamable HTTP is opt-in (ADR-0006) — requires bearer gate token; disabled by default.
- Do not point MCP clients at
/metricsor/healthz— those are operator endpoints, not MCP.
Security incidents¶
Report vulnerabilities privately per SECURITY.md.