Dev MCP settings page now recommends Quarkus Agent MCP#53764
Dev MCP settings page now recommends Quarkus Agent MCP#53764phillip-kruger wants to merge 2 commits intoquarkusio:mainfrom
Conversation
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
e2ecf86 to
e178363
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
🎊 PR Preview b3ff96b has been successfully built and deployed to https://quarkus-pr-main-53764-preview.surge.sh/version/main/guides/
|
e178363 to
9d660da
Compare
9d660da to
8c423ad
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
cescoffier
left a comment
There was a problem hiding this comment.
Do you think we could have a badge counting the number of connections?
- Add JBang prerequisite and verification step to docs - Rename "Direct connection (advanced)" to "Connect an MCP client" - Use jbang on PATH instead of absolute path for JetBrains config - Update Dev UI label from "Advanced: Direct connection" to "Direct connection"
Status for workflow
|
Status for workflow
|
| Status | Name | Step | Failures | Logs | Raw logs | Build scan |
|---|---|---|---|---|---|---|
| ❌ | JVM Tests - JDK 17 | Build |
Failures | Logs | Raw logs | 🔍 |
| ✔️ | JVM Tests - JDK 21 | Logs | Raw logs | 🔍 | ||
| ✔️ | JVM Tests - JDK 25 | Logs | Raw logs | 🔍 | ||
| ✔️ | JVM Tests - JDK 25 Semeru | Logs | Raw logs | 🔍 |
Full information is available in the Build summary check run.
You can consult the Develocity build scans.
Failures
⚙️ JVM Tests - JDK 17 #
- Failing: extensions/devui/deployment
📦 extensions/devui/deployment
❌ io.quarkus.devui.devmcp.DevMcpTest.testClearLastException - History - More details - Source on GitHub
Details
io.quarkus.dev.appstate.ApplicationStartException: java.lang.RuntimeException: Failed to start quarkus
at io.quarkus.dev.appstate.ApplicationStateNotification.waitForApplicationStart(ApplicationStateNotification.java:63)
at io.quarkus.runner.bootstrap.StartupActionImpl.runMainClass(StartupActionImpl.java:189)
at io.quarkus.deployment.dev.IsolatedDevModeMain.firstStart(IsolatedDevModeMain.java:92)
at io.quarkus.deployment.dev.IsolatedDevModeMain.accept(IsolatedDevModeMain.java:436)
at io.quarkus.deployment.dev.IsolatedDevModeMain.accept(IsolatedDevModeMain.java:56)
at io.quarkus.bootstrap.app.CuratedApplication.runInCl(CuratedApplication.java:157)
at io.quarkus.bootstrap.app.CuratedApplication.runInAugmentClassLoader(CuratedApplication.java:98)

The Dev MCP settings page in Dev UI previously showed how to connect coding agents directly to the Dev MCP HTTP endpoint on the running app. With the quarkus-agent-mcp now available as a standalone project, this is no longer the recommended approach.
The page now has two sections:
Quarkus Agent MCP (primary) — shows configuration snippets for 9 agents/IDEs (Claude Code, Cursor, VS Code, Claude Desktop, Cline, Goose, Windsurf, Zed, JetBrains) using
jbang quarkus-agent-mcp@quarkusiovia stdio. Includes a JBang prerequisite note. This section is always visible regardless of whether Dev MCP is enabled.Dev MCP Server (secondary) — shows the enable/disable toggle, connected clients, and a collapsible "Advanced: Direct connection" panel with the URL-based configs for connecting directly to the running app's Dev MCP endpoint.