Upgrading MCP Connector to Version 1.0.0
MCP Connector 0.1.0-BETA is deprecated. Use MCP Connector 1.0.0 instead. MCP Connector 1.0.0 is not backward-compatible with the 0.1.0-BETA version of this connector.
Changes in This Release
This release contains the following changes:
-
Streamable HTTP Transport
Support for Streamable HTTP transport is added. This transport method replaces the deprecated SSE transport for better scalability and cloud compatibility.
-
Custom Response Headers
Added support for custom headers on all exposed endpoints.
-
Enhanced Error Handling
Improved error handling with specific error types and better error messages.
-
Performance Improvements
Added caching support and timeout configurations.
-
Input Validation
Enhanced parameter validation with JSON schema constraints.
-
These new types are added:
-
Call Tool Response
-
Resource Content
-
Resource Metadata
-
Tool Metadata
-
New Session Request
-
Resource Request
-
Text Tool Response Content
-
Text Resource Tool Response Content
-
Blob Resource Tool Response Content
-
Blob Resource
-
-
The
mule.http.service.implementation=NETTYproperty is no longer required and must be removed. -
The
<mcp:resource-content>element under<mcp:resource-listener>is renamed to<mcp:resource-listener-content>. If you used the 0.1.0-BETA version of this connector, you must manually rename the element in the connector’s configuration XML.
Removed Features
-
The
<mcp:resource-capabilities>and<mcp:tool-capabilities>configuration attributes are removed. -
The
<mcp:add-dynamic-resource>operation is removed. The MCP server always advertises itself as non-dynamic.
Update the POM File Dependency
If you are using MCP Connector 0.1.0-BETA, you must update your POM file dependency to:
<dependency>
<groupId>com.mulesoft.connectors</groupId>
<artifactId>mule-mcp-connector</artifactId>
<version>1.0.0</version>
<classifier>mule-plugin</classifier>
</dependency>Note that the <groupId>com.mulesoft.connector</groupId> is changed so that connector is now plural connectors.