Expose DevUI's capabilities as MCP functions

[phillip-kruger]

The PR introduces the ability to expose capabilities of the DevUI as MCP tools (and others), essentially making
a Quarkus application running in Dev Mode an MCP server.

Screencast_20250722_133945.mp4

Screencast_20250724_144657.mp4

TODO:

• Making sure the Streamable Endpoint is handling all requests expected from Goose or similar.
• Implement the resources from build time data
• Implement the resources from recorded values
• Implement the resourcesTemplates from Workspace Items
• Add the parameters to the runtime tools
• Add the parameters to the deployment tools
• If the auto description is not enough, find a way to add descriptions.
• Maybe have a filter to filter out some methods to not be used in MCP ?
• Populate the Dev UI MCP Server page with info on how to use this.

[github-actions]

🎊 PR Preview 55e0ee3 has been successfully built and deployed to https://quarkus-pr-main-47414-preview.surge.sh/version/main/guides/

• Images of blog posts older than 3 months are not available.
• Newsletters older than 3 months are not available.

[geoand]

This has so much potential and we should do whatever we can to get it up and running ASAP!

One thing I see that we will need is to also be able to provide metadata for tool arguments, not just the tool method itself. Never mind, I just saw that @JsonRpcDescription can also be applied to method params.

[geoand]

Making sure the SSE Endpoint is handling all requests expected from Goose or similar.

Is this missing entirely or is it just not working currently? Asking because I didn't anything relevant in the code

[phillip-kruger]

@cescoffier @geoand - I think we are good to to for the initial version:

• Only dev-ui internal json-rpc methods has been exposed as mcp (by adding a description)
• By default (for now) the mcp server is disabled. You need to switch this on with config. This will allow us to play with this until we are happy.
• Resource is also working. I have only tested with the "info" extension. We can add more resources from other extensions in followup PRs.
• I'll add and update documentation in a follow up PR.
• I'll follow up with PRs for each extension to expose their relevant json-rpc methods as mcp.

There are still a few things we can implement, like promps, resourceTemplates and certain notifications (we would need SSE for that). But I think this is a workable start.

[phillip-kruger]

Also /cc @mkouba

[geoand]

This is so neat!

+1 for getting in now and improving it iteratively

[quarkus-bot]

Status for workflow Quarkus Documentation CI

This is the status report for running Quarkus Documentation CI on commit f6fc52d.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

Warning

There are other workflow runs running, you probably need to wait for their status before merging.

[quarkus-bot]

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit f6fc52d.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

You can consult the Develocity build scans.

[cescoffier]

LGTM - make sure this is marked experimental.