Also did some major cleanup and released quarkus-flags 1.0.0.CR1! 😉 docs.quarkiverse.io/quarkus-flag...
It does not implement MCP 2025-11-25, that's a plan for 1.9+ 😉.
⚡ Quarkus MCP Server 1.13.0 is out!
- Elicitation URL mode (MCP 2025-11-25)
- Streamable HTTP: lazy SSE init + auto-init now honors client capabilities
- New quarkus-mcp-server-oidc extension
- OptionalInt/Long/Double support for tool params
github.com/quarkiverse/...
🔔🗞️We've released #quarkus MCP server 1.12.0 with OpenTelemetry tracing integration, relaxed uniqueness constraints for feature names, convenient tools to test STDIO-based MCP servers with McpAssured API, bug fixes and perf improvements:
github.com/quarkiverse/...
📣 I've created a new #quarkiverse extension - quarkus-flags, a lightweight and extensible feature flags/toggles/switches #quarkus extension: github.com/quarkiverse/... Feedback, feature requests and contributions are welcome🙏.
❄️ #quarkus MCP server 1.8.0 is here with a bunch of bug fixes, WrapBusinessError#unless(), quarkus-mcp-server-sse was renamed to quarkus-mcp-server-http but old artifactId and config should still work thanks to relocations, and more: github.com/quarkiverse/...
💥 #quarkus MCP server 1.9.0 released with some of the 2025-11-25 features, Tool input/output guardrails, improved test coverage, bunch of bug fixes, and more: github.com/quarkiverse/...
👋#quarkus MCP server 1.11.0 is out, with repeatable McpServer annotation, convenient elicitation builders, configurable tool names validation, revised dummy/auto initialization for streamable HTTP, JSON schema validation, MCP Conformance test server etc.: github.com/quarkiverse/...
If you want to test the business logic of your components in isolation, with different configurations and inputs, then QuarkusComponentTest is a good choice. It’s fast, integrated with continuous testing, and extensible. Learn more with this blog post by Martin Kouba
quarkus.io/blog/quarkus...