Tracking latest MCP specification

[starksm64]

I saw the latest blog from the MCP protocol blog:
https://blog.modelcontextprotocol.io/posts/2026-07-28-release-candidate/

and noted that this is quite a big change and called out as backwards incompatible, and due to be final next week. I did not find a Quarkus issue tracking the next rev of MCP. When one is created can you drop it in here?

Thanks

[sberyozkin]

@starksm64 Hi Scott, should we discuss it at https://github.com/quarkiverse/quarkus-mcp-server ?

FYI, I reviewed the authorization part last week, optional iss query parameter in the code flow response will indeed be done at the Quarkus level. Some scope related optimizations in WWW-Authenticate might be tuned at the quarkus-mcp-server level. To be honest I don't see much more work for the MCP server, except for the stable https://github.com/modelcontextprotocol/ext-auth/blob/main/specification/stable/enterprise-managed-authorization.mdx that everyone seems to want immediately right now, so we'll handle it too.

@mkouba Hi Martin, can you open Discussions please ?

[cescoffier]

@starksm64 we have already started implementing the release candidate. It's version 2.0 of the MCP server. We will release a GA once the spec graduates.

[mkouba]

Hi Martin, can you open Discussions please ?

We don't use github discussions in quarkus-mcp-server.

@starksm64 we have already started implementing the release candidate. It's version 2.0 of the MCP server. We will release a GA once the spec graduates.

Right, we released 2.0.0.Beta3 three weeks ago and the plan is to release 2.0.0.CR1 later this week.

[mkouba]

We've released 2.0.0.CR1 today!