Can AI agents automate IBM MQ?
IBM · hybrid · enterprisecommunications
IBM MQ is automatable today through the administrative REST API on the mqweb server. IBM documents JSON administration of queue managers, queues, and Managed File Transfer, and POST of MQSC to /ibmmq/rest/v3/admin/action/qmgr/{qmgrName}/mqsc. Callers authenticate with HTTP basic (Authorization header; ibm-mq-rest-csrf-token on POST, PATCH, or DELETE) or an LTPA cookie from the login resource, and must be in MQWebAdmin, MQWebAdminRO, or MQWebUser. The GET queue resource documents inquire-style queue reads and names AIX, Linux, and Windows authority commands. That surface is administration, not application payload put or get. The first-party ibm-messaging/mq-mcp-server, listed on IBM/mcp, exposes two tools only: dspmq (GET admin/qmgr/) and runmqsc (POST MQSC). The README calls the project a sample MCP server. Those tools check queue-manager health and run MQSC; they are not a message-payload API. This record is IBM MQ as presented on the MQ 10.0 product page. It is not Kafka. iPaaS connectors were not opened. Computer-use viability is unassessed. API scores 7 and is the best path. MCP scores 5 because the official server is a two-tool health-and-MQSC wrapper.
Best path today: api · Overall automatability: 7/10
Modalities
| Modality | Status | Detail |
|---|---|---|
| API | yes | restbasicltpa-token coverage: partial · docs |
| SDK | unknown | official: unknown |
| MCP | yes | verdict: official |
| Integrations | unknown | |
| CLI | unknown | |
| Extensibility | unknown | webhooks: unknown |
| Data access | export: json · import: unknown | |
| RPA / UI automation | unknown | No repeatable UI probe was run. The administrative REST API and the first-party MQ MCP server (health and MQSC only) are the supported automation paths. The MQ Console UI remains unassessed.
|
| Computer use | unknown | measured verdicts only — "unknown" means not yet probed by us |
Scores
| api | mcp | integrations | cli | rpa | computer use | overall |
|---|---|---|---|---|---|---|
| 7 | 5 | — | — | — | — | 7 |
Evidence
| Fact | Tier | Source | Date |
|---|---|---|---|
homepage | declared | source | 2026-09-11 |
deployment | declared | source | 2026-09-11 |
platforms | declared | source | 2026-09-11 |
license | declared | source | 2026-09-11 |
status | declared | source | 2026-09-11 |
modalities.api.exists | declared | source | 2026-09-11 |
modalities.api.kinds[0] | declared | source | 2026-09-11 |
modalities.api.auth[0] | declared | source | 2026-09-11 |
modalities.api.auth[1] | declared | source | 2026-09-11 |
modalities.api.coverage | declared | source | 2026-09-11 |
modalities.api.coverage | declared | source | 2026-09-11 |
modalities.api.docs | declared | source | 2026-09-11 |
modalities.data_access.export[0] | declared | source | 2026-09-11 |
modalities.mcp.first_party | declared | source | 2026-09-11 |
modalities.mcp.first_party | declared | source | 2026-09-11 |
modalities.mcp.verdict | declared | source | 2026-09-11 |
verdict.scores.api | declared | source | 2026-09-11 |
verdict.scores.mcp | declared | source | 2026-09-11 |
freshness.watch[0].url | declared | source | 2026-09-11 |
freshness.watch[1].url | declared | source | 2026-09-11 |
freshness.watch[2].url | declared | source | 2026-09-11 |
freshness.watch[3].url | declared | source | 2026-09-11 |
freshness.watch[4].url | declared | source | 2026-09-11 |
freshness.watch[5].url | declared | source | 2026-09-11 |
Related tools
Other products in this database that share a category with IBM MQ.
Last verified 2026-09-11 · volatility medium · JSON record