echooymxq opened a new pull request, #998:
URL: https://github.com/apache/rocketmq-dashboard/pull/998

   ## What is the purpose of the change
   
     This PR introduces RocketMQ Studio's MCP and CLI entrypoints on top of the 
existing AI Tool Catalog.
   
     The goal is to make RocketMQ Studio operational capabilities discoverable 
and invokable through a single tool contract that can be shared by Web, AI, MCP 
clients, and the new `rmqctl` CLI. The server side now validates tool 
input/output schemas, filters tools by cluster capability, exposes catalog 
metadata headers, and provides MCP tool specifications backed by the same Tool 
Gateway execution path.
   
     ## Brief changelog
   
     - Add the `rmqctl` CLI module with profile configuration, table/json 
output, and Studio-backed commands for clusters, topics, consumer groups, 
dashboard summaries, alert rules, and tool calls.
     - Add MCP support for Studio tools, including MCP tool registration, JSON 
Schema mapping, tool annotations, execution metadata, and `rmqctl mcp stdio` 
proxy support.
     - Extend `/api/ai/tools` and `/api/ai/tools/call` with catalog metadata 
headers and structured tool execution results.
     - Add Tool Runtime execution policy handling, stable error codes, 
risk-level metadata, cluster capability checks, and schema-based input/output 
validation.
   
   Follow this checklist to help us incorporate your contribution quickly and 
easily. Notice, `it would be helpful if you could finish the following 5 
checklist(the last one is not necessary)before request the community to review 
your PR`.
   
   - [x] Make sure there is a [Github 
issue](https://github.com/apache/rocketmq/issues) filed for the change (usually 
before you start working on it). Trivial changes like typos do not require a 
Github issue. Your pull request should address just this issue, without pulling 
in other changes - one PR resolves one issue. 
   - [x] Format the pull request title like `[ISSUE #123] Fix UnknownException 
when host config not exist`. Each commit in the pull request should have a 
meaningful subject line and body.
   - [x] Write a pull request description that is detailed enough to understand 
what the pull request does, how, and why.
   - [x] Write necessary unit-test(over 80% coverage) to verify your logic 
correction, more mock a little better when cross module dependency exist. If 
the new feature or significant change is committed, please remember to add 
integration-test in [test 
module](https://github.com/apache/rocketmq/tree/master/test).
   - [x] Run `mvn -B clean apache-rat:check findbugs:findbugs 
checkstyle:checkstyle` to make sure basic checks pass. Run `mvn clean install 
-DskipITs` to make sure unit-test pass. Run `mvn clean test-compile 
failsafe:integration-test`  to make sure integration-test pass.
   - [x] If this contribution is large, please file an [Apache Individual 
Contributor License Agreement](http://www.apache.org/licenses/#clas).
   


-- 
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]

Reply via email to