X-LightYear opened a new issue, #7209: URL: https://github.com/apache/rocketmq-dashboard/issues/7209
## Problem The mq.topic.list and mq.group.list MCP tools expose instance and resource-name filters, but not the physical clusterId filter. Their existing MetadataService and REST paths already support cluster-scoped listing. In an instance containing multiple RocketMQ clusters, an MCP planner cannot constrain either list to one physical cluster and receives cross-cluster results. ## Expected behavior Both tools should accept an optional clusterId and forward it to the existing cluster-aware metadata service methods. Omitting it must preserve the current all-cluster behavior. ## Scope This change only completes the MCP input contract and handler forwarding; provider and REST behavior are unchanged. The catalog documents the filter and deterministic handler/catalog tests cover both tools. ## Verification The focused server test suite passes 9 tests with checkstyle clean using -Dmaven.compiler.proc=full. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
