MCP Registry for Extensions

[myfear]

Description

I wanted to take a look at the new Dev UI MCP feature today and realized, that I don't even know which extensions provide an MCP endpoint.
I would love to have a way to find that out. Either via documentation (not on the individual extension but centrally) or any other way.

Implementation ideas

No response

[quarkus-bot]

/cc @cescoffier (devui), @phillip-kruger (devui,mvnpm)

[phillip-kruger]

Hi @myfear . Dev MCP is part of Dev UI, that you get by adding at least Vertx HTTP (Usually this gets pulled in transitively). Then, depending on the extensions added by your application, you will have a set of methods available in your Dev MCP server. See https://quarkus.io/guides/dev-mcp

[myfear]

Thank you @phillip-kruger ! I think, I do understand that.
And I also learned about the MCP tools overview page.
I think, what I was missing is the info about which extension brings what kind of MCP tool.
Maybe that would be an addition to both the extension documentation and the MCP tool overview page.
Especially, as llm's won't be able to handle an unlimited amount of tools. I think it would be extra cool, if
we could enable/disable "a set of" tools in the mcp overview.

[phillip-kruger]

Yes, enable/disable is on the todo list. It would be great to get to that point, as that would mean that many extensions has added mcp support:) If you are keen, please provide a PR with the documentation enhancements you want, that will help a lot. In the mean time I'll look into the enable/disable feature.

[cescoffier]

I would like to add that this is just the early steps. As Phillip said, we need the "enable/disable" configuration, in addition to detecting and rewriting functions that produce too much content (filling the context window).