You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: posts/2026-05-05-26.0.0.5-beta.adoc
+20-69Lines changed: 20 additions & 69 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -44,21 +44,20 @@ The link:{url-about}[Open Liberty] 26.0.0.5-beta includes the following beta fea
44
44
See also link:{url-prefix}/blog/?search=beta&key=tag[previous Open Liberty beta blog posts].
45
45
46
46
// // // // DO NOT MODIFY THIS COMMENT BLOCK <GHA-BLOG-TOPIC> // // // //
47
-
// Blog issue: https://github.com/OpenLiberty/open-liberty/issues/33838
47
+
// Blog issue: https://github.com/OpenLiberty/open-liberty/issues/34763
48
48
// Contact/Reviewer: martindrozdz
49
49
// // // // // // // //
50
50
[#mcp]
51
51
== Updates to `mcpServer-1.0`
52
52
53
-
The link:https://modelcontextprotocol.io/docs/getting-started/intro[Model Context Protocol (MCP)] is an open standard that enables AI applications to access real-time information from external sources. The Liberty MCP Server feature `mcpServer-1.0` allows developers to expose the business logic of their applications, allowing it to be integrated into agentic AI workflows.
53
+
The link:https://modelcontextprotocol.io/docs/getting-started/intro[Model Context Protocol (MCP)] is an open standard that enables AI applications to access real-time information from external sources. The Liberty MCP Server feature `mcpServer-1.0` allows developers to expose the business logic or data from their applications, allowing it to be integrated into agentic AI workflows.
54
54
55
55
This beta release of Liberty includes important updates to the `mcpServer-1.0` feature, including configurable endpoint paths and notable bug fixes.
56
56
57
57
=== Prerequisites
58
58
To use the `mcpServer-1.0` feature, it is required to have `Java 17` or later installed on your system.
Previously, the MCP endpoint was hard-coded to `/mcp` under the web application context root. You can now configure custom endpoint paths to better suit your application architecture and naming conventions.
63
62
64
63
==== Single Application Configuration
@@ -67,76 +66,30 @@ For a single application, configure the endpoint path directly in the `<mcpServe
67
66
68
67
[source,xml]
69
68
----
70
-
<server description="Liberty server with custom MCP endpoint">
69
+
<server description="Configurable Mcp Path Liberty server">
With this configuration, MCP server can be accessed at `/custom-mcp` instead of the default `/mcp` path.
89
87
90
-
==== Multiple Application Configuration
91
-
92
-
For applications with multiple modules or when you need different endpoint paths for different parts of your application, configure the MCP server settings under the `<application>` element:
93
-
94
-
[source,xml]
95
-
----
96
-
<server description="Liberty server with multiple MCP endpoints">
* Define different endpoint paths for different modules within the same application
120
-
* Use descriptive paths that align with your API structure
121
-
* Support future extensibility for multiple MCP endpoints within a single module
122
-
123
-
==== Configuration Options
88
+
=== Configuration Options
124
89
125
90
The `<mcpServer>` element supports the following attributes:
126
91
127
-
* *endpoint* (single app): The custom path for the MCP endpoint (e.g., `/custom-mcp`)
128
-
* *moduleName* (multi-app): The name of the module to configure
129
-
* *name* (multi-app): The identifier for the MCP server configuration (typically "default")
130
-
* *path* (multi-app): The custom path for the MCP endpoint
131
-
132
-
==== Benefits
133
-
134
-
Configurable endpoint paths provide:
135
-
136
-
* *Flexibility*: Align MCP endpoints with your existing API structure
137
-
* *Multi-tenancy support*: Different paths for different applications or modules
138
-
* *Future-proofing*: Foundation for supporting multiple MCP endpoints per application
139
-
* *Better organization*: Descriptive paths that reflect the purpose of each endpoint
92
+
- **path** (single app): The custom path for the MCP endpoint (for example, `/custom-mcp`)
140
93
141
94
=== Notable bug fixes in this release for `mcpServer-1.0`
142
95
@@ -194,8 +147,8 @@ This has been fixed to ensure proper isolation of encoder beans per application,
194
147
// DO NOT MODIFY THIS LINE. </GHA-BLOG-TOPIC>
195
148
196
149
// // // // DO NOT MODIFY THIS COMMENT BLOCK <GHA-BLOG-TOPIC> // // // //
197
-
// Blog issue: https://github.com/OpenLiberty/open-liberty/issues/33838
198
-
// Contact/Reviewer: martindrozdz
150
+
// Blog issue: https://github.com/OpenLiberty/open-liberty/issues/34374
151
+
// Contact/Reviewer: rangaran
199
152
// // // // // // // //
200
153
[#transportSecurity]
201
154
== Transport Security
@@ -204,27 +157,24 @@ Liberty uses the default cipher list from the JDK. The `securityLevel` attribute
204
157
205
158
This change modifies the existing attribute `enabledCiphers` in the `ssl` config.
206
159
207
-
Liberty's `securityLevel` based cipher categories no longer provide meaningful value. The `MEDIUM` and `LOW` categories contain no remaining ciphers and `securityLevel` `HIGH` does not sync up (or not the same) with/as the JDK defaults.
160
+
Liberty's `securityLevel` based cipher categories no longer provide meaningful value. The `MEDIUM` and `LOW` categories contain no remaining ciphers.
208
161
209
-
The `enabledCiphers` attribute includes a new syntax option to add '+' or remove '–' specific ciphers from the JDK default list without redefining everything. A static list and +/- syntax in the same `enabledCiphers` entry is not allowed. If the value set in `enabledCiphers` contains a static entry and a +/- entry, an error is logged, and the server ignores the `enabledCiphers` value by returning the JDK default list.
162
+
The `enabledCiphers` attribute includes a new syntax option to add '+' or remove '–' specific ciphers from the effective JDK cipher list without redefining everything. A static list and +/- syntax in the same `enabledCiphers` entry is not allowed. If the value set in `enabledCiphers` contains a static entry and a +/- entry, an error is logged, and the server ignores the `enabledCiphers` value by returning the effective JDK cipher list.
To learn more about Transport Security, see link:https://openliberty.io/docs/modules/reference/23.0.0.6/com.ibm.websphere.appserver.api.ssl_1.5-javadoc/com/ibm/websphere/ssl/Constants.html[SSL Constants Javadoc], link:https://openliberty.io/docs/modules/reference/23.0.0.6/com.ibm.websphere.appserver.api.ssl_1.5-javadoc/com/ibm/websphere/ssl/JSSEProvider.html[JSSEProvider Javadoc], and link:https://openliberty.io/docs/latest/reference/config/ssl.html[SSL Configuration Reference].
@@ -234,7 +184,8 @@ To learn more about Transport Security, see link:https://openliberty.io/docs/mod
234
184
[#run]
235
185
=== Try it now
236
186
237
-
To try out these features, update your build tools to pull the Open Liberty All Beta Features package instead of the main release. The beta works with Java SE 21, Java SE 17, Java SE 11, and Java SE 8.
187
+
To try out these features, update your build tools to pull the Open Liberty All Beta Features package instead of the main release. To enable the MCP server feature, follow the instructions from link:https://openliberty.io/blog/2025/10/23/mcp-standalone-blog.html[MCP standalone blog]. The beta works with Java SE 25, Java SE 21, Java SE 17, Java SE 11, and Java SE 8.
188
+
238
189
// // // // // // // //
239
190
// In the preceding section:
240
191
// Check if a new non-LTS Java SE version is supported that needs to be added to the list (21, 17, 11, and 8 are LTS and will remain for a while)
0 commit comments