On 17 Jun 2026, at 18:22, Brian Stansberry <bstansbe@redhat.com> wrote:
This Message Is From an External SenderThis message came from outside your organization.Excellent! It's great to see this happening.
If you need help with the Nexus stuff let me know. Also, I have some private documents related to how various projects deploy to Nexus that I'll want to update.
On Wed, Jun 17, 2026 at 3:42 AM Jean-Frederic Mesnil <jmesnil@ibm.com> wrote:
Hi,
We have made good progress on this proposal. The feature pack has been updated to be at the experimental stability overall.Dimitris and Emmanuel have implemented a lot of the remaining features for the 2025-11-25 MCP prototocol too.
We’re not ready yet to promote the MCP server features at the default stability level. We rely on a Java library for MCP annotations and API that is not final and there is a new MCP protocol around the corner. We need to have a plan to implement this new protocol in a stable manner before we can really provide it as a stable feature…
Still, I think we are at the point where this project can move from the wildfly-extras to the wildfly organization.This transfer is transparent for users but this has a few impact for developers:
* It will change the nexus deployment process* It will allow us to publish documentation for this feature pack at docs.wildfly.org
I’m planning to transfer the project later today.Github handles nicely the redirection but I’ll send another message when the transfer is done so that we can allpoint directly to the repo in the github.com/wildfly organization.
After this transfer, we will be able to release a new version of the feature pack.It *will* be a breaking change as users will have to provision and run WildFly at the experimental stability level (and the API as been updated for some advanced MCP server features such as elicitation).
Best regards,Jeff
On 20 May 2026, at 15:47, Brian Stansberry <bstansbe@redhat.com> wrote:
This Message Is From an External SenderThis message came from outside your organization.Great!
On Wed, May 20, 2026 at 7:59 AM Jean-Frederic Mesnil via wildfly-dev <wildfly-dev@lists.jboss.org> wrote:
I’ve created the proposal at https://github.com/wildfly/wildfly-proposals/issues/829_______________________________________________I’d like to get this feature done for WildFly 41 which as a very short dev cycle so, to achieve this, we will do 2 things at once:
* move all features in AI feature pack to the experimental stability level* promote the MCP server features to stability level.
Jeff
On 20 May 2026, at 10:00, Jean-Frederic Mesnil via wildfly-dev <wildfly-dev@lists.jboss.org> wrote:
Hi,
I’ve created a new issue to promote MCP server features to default stability level[1].
The intent is to make WildFly a MCP server where users could integrate their applications as MCP server resources (tools, resources) and open them to AI ecosystem.
The scope is narrow and focuses only on MCP server features.
The code has been in development for quite some time and we are in the process of implementing the latest MCP server specification.
As part of this promotion, we need to iron out the code, fill gaps in the testing, provide documentation, etc. as described in our feature process document[2].
Only features and packages of the WildFly AI feature pack that provides MCP server capabilities are planned to move to default stability level.
There are many other capabilities (including MCP client, LLM, WASM) provided by the feature pack that will remain at the experimental level.
Best regards,
Jeff
[1] https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_wildfly_wildfly-2Dproposals_issues_829&d=DwIGaQ&c=BSDicqBQBDjDI9RkVyTcHQ&r=hY9ssjZOzTr6nBT17SjZxQ&m=jSCzd0MZbqh96SivLlh6MJAN7_XakJDKPYimbe9Z47fRdULwLM9gt_gh1AJi6UFu&s=jcwnotgvbCd7LMiIcbE_Pmth_WPMGtyVyzFqk5uezpI&e=
[2] https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.wildfly.org_wildfly-2Dproposals_FEATURE-5FPROCESS.html&d=DwIGaQ&c=BSDicqBQBDjDI9RkVyTcHQ&r=hY9ssjZOzTr6nBT17SjZxQ&m=jSCzd0MZbqh96SivLlh6MJAN7_XakJDKPYimbe9Z47fRdULwLM9gt_gh1AJi6UFu&s=-XXELC7xeXb4VCI_kDrJJ0azHVY4QuSu7--E6HQxSTQ&e=
--
Jeff Mesnil
Software Engineer
Red Hat JBoss EAP
https://urldefense.proofpoint.com/v2/url?u=http-3A__jmesnil.net_&d=DwIGaQ&c=BSDicqBQBDjDI9RkVyTcHQ&r=hY9ssjZOzTr6nBT17SjZxQ&m=jSCzd0MZbqh96SivLlh6MJAN7_XakJDKPYimbe9Z47fRdULwLM9gt_gh1AJi6UFu&s=skfvSiKU9IvVhWbKvKmmlkIOvLcduh8fOJxaUCbee1g&e=
IBM
Unless otherwise stated above:
Compagnie IBM France
Siège Social : 17, avenue de l'Europe, 92275 Bois-Colombes Cedex
RCS Nanterre 552 118 465
Forme Sociale : S.A.S.
Capital Social : 664 614 175,50 €
SIRET : 552 118 465 03644 - Code NAF 6203Z
_______________________________________________
wildfly-dev mailing list -- wildfly-dev@lists.jboss.org
To unsubscribe send an email to wildfly-dev-leave@lists.jboss.org
Privacy Statement: https://urldefense.proofpoint.com/v2/url?u=https-3A__www.redhat.com_en_about_privacy-2Dpolicy&d=DwIGaQ&c=BSDicqBQBDjDI9RkVyTcHQ&r=hY9ssjZOzTr6nBT17SjZxQ&m=jSCzd0MZbqh96SivLlh6MJAN7_XakJDKPYimbe9Z47fRdULwLM9gt_gh1AJi6UFu&s=Twcb85umtfE-CoXfIw8beg6mOyC2c2kV6utJUil8wSg&e=
List Archives:
Unless otherwise stated above:
Compagnie IBM France
Siège Social : 17, avenue de l'Europe, 92275 Bois-Colombes Cedex
RCS Nanterre 552 118 465
Forme Sociale : S.A.S.
Capital Social : 664 614 175,50 €
SIRET : 552 118 465 03644 - Code NAF 6203Z
wildfly-dev mailing list -- wildfly-dev@lists.jboss.org
To unsubscribe send an email to wildfly-dev-leave@lists.jboss.org
Privacy Statement: https://www.redhat.com/en/about/privacy-policy
List Archives:
--
Brian StansberryCollaborative Partner - IBM
Architect, JBoss EAPWildFly Project LeadHe/Him/His
Unless otherwise stated above:
Compagnie IBM France
Siège Social : 17, avenue de l'Europe, 92275 Bois-Colombes Cedex
RCS Nanterre 552 118 465
Forme Sociale : S.A.S.
Capital Social : 664 614 175,50 €
SIRET : 552 118 465 03644 - Code NAF 6203Z
--
Brian StansberryCollaborative Partner - IBM
Architect, JBoss EAPWildFly Project LeadHe/Him/His