Contact Us 1-800-596-4880
  1. Homepage
  2. MCP Connector (1.6)

  3. Upgrading and Migrating MCP Connector

All Connectors

Upgrading MCP Connector to Version 1.6

MCP Connector 0.1.0-BETA is deprecated. Use MCP Connector 1.x instead. MCP Connector 1.x is not backward-compatible with the 0.1.0-BETA version of this connector.

Supported Upgrade Paths

From Version To Version

1.0

1.x

Changes in 1.6

  • MCP Connector now includes the MCP Server - Create Elicitation operation and the MCP Client - Elicitation Listener source.

    These capabilities implement the MCP elicitation protocol so servers can request additional structured input from clients during tool and resource execution.

  • Elicitation is opt-in through the new Enable Elicitations field on the client configuration.

    For multi-worker deployments, use Streamable HTTP server transport and configure an Object Store on the server connection so elicitation correlation is preserved across workers. SSE server transport is single-worker only.

  • Server connection configuration now includes the new Elicitation Timeout Seconds, Elicitations Object Store, and Elicitation Polling Seconds fields to route elicitation responses across replicas.

  • The MCP Client - List Tools, MCP Client - List Resources, and MCP Client - List Prompts operations now include the new Additional Properties field.

    Pass custom headers, correlation IDs, tenant identifiers, or other metadata on list calls. The values are propagated to the corresponding server-side listeners and are accessible from attributes.additionalProperties.

Changes in 1.5

  • MCP Connector now includes the MCP Client - Get Prompt and MCP Client - List Prompts operations, and the MCP Server - Prompt Listener source.

    Expose server-side prompt templates with typed arguments and consume them from clients, with responses supporting text, image, embedded resource, and resource link content.

  • The MCP Client - Call Tool operation now includes the new Extract Structured Content field.

    Define tool parameter and output schemas using either inline JSON or external files, fully supported by robust design-time schema validation. With this, the connector now also includes the new MCP:SCHEMA_VALIDATION_FAILED error.

  • The connector now includes response attributes to support structured client-side error handling with HTTP response details. With this, the connector now also includes the new MCP:UNAUTHORIZED error.

Changes in 1.4

  • The MCP Java SDK is upgraded to the latest release version (1.0.0).

  • Both the server and client transports now default to 2025-06-18 as the preferred version of the protocol.

  • Both the server and client transports now set the Mcp-Protocol-Version header to the version negotiated upon connection initialization.

Changes in 1.3

  • The MCP Server - On New Session Listener source now supports custom rejection headers with the new Reject With Headers field.

Changes in 1.2

  • MCP Connector now supports distributed tracing.

Changes in 1.1

  • A Default Request Headers parameter is added to both the SSE Client and Streamable Http Client connection types within the MCP Client configuration. Use this parameter to specify custom headers to send with every request to the MCP server.

Changes in 1.0

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=NETTY property 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.

Remove the NETTY Property

If you used the 0.1.0-BETA version of MCP Connector and added the -Dmule.http.service.implementation=NETTY property, remove it anywhere you added it, including the:

  • AnypointStudio.ini file

  • Debug configuration

  • Apps' properties

See Also

Back to top