X-LightYear opened a new issue, #5016: URL: https://github.com/apache/rocketmq-dashboard/issues/5016
## Problem RocketMQ Studio already exposes the managed instance directory through `GET /api/instances`, and the web console uses it to select a canonical Studio instance. The MCP catalog exposes `rmq.instance.capabilities`, but it requires an `instanceId` before an agent can discover which managed instances exist. In a multi-instance deployment, an MCP planner therefore cannot reliably choose the canonical target needed by the rest of the instance-scoped tools. ## Expected behavior Expose the existing managed-instance directory as a read-only MCP tool so an operator or planner can discover valid Studio instance targets before calling instance-scoped tools. The tool should: - reuse `InstanceService.listInstances` and its existing `type` / `search` filters; - return the canonical instance name, vendor, access type, region, resource counts, and count availability; - omit credentials and credential references from the MCP projection; - remain platform-level and read-only, without requiring an instanceId or introducing new persistence/provider behavior. ## Production reachability The source capability is already reachable through `InstanceController.listInstances` at `GET /api/instances`. `InstanceService.listInstances` is exercised by the console and fills resource counts through the registered provider, marking counts unavailable when a provider lookup fails instead of failing the whole directory response. ## Scope Add the catalog contract, handler, safe output projection, and focused contract/handler coverage for `rmq.instance.list`. This is an MCP discovery completion using an existing REST/service capability; it does not change instance selection, provider behavior, or credential storage. ## Validation plan - verify the catalog declares a platform-level read-only tool; - verify type/search arguments are delegated to `InstanceService`; - verify realistic Apache/cloud fixtures project operational fields and no credential fields; - verify the output against the catalog schema and the existing tool registration path. This is separate from #4957: that issue concerns the frontend Playground using physical cluster IDs as instance targets, while this issue adds server-side MCP discovery of the managed-instance directory. -- 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]
