---
schema_version: "1"
id: b6597b228f9618f52ab7627c544cd8ac27c17a5d7e1ba004200dd6f4fbbfcd83
title: Upgrading MCP Connector to Version 1.5
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/mcp-connector/1.5/mcp-connector-upgrade-migrate.md
canonical_url: https://docs.mulesoft.com/mcp-connector/1.5/mcp-connector-upgrade-migrate
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 36983577afd3d3f891683c7d7dc649320158cef85a1256c46551fe30d35707ab
description: MuleSoft Documentation Site
release: "1.5"
latest: false
---
---
product: MCP Connector
version: 1.5
---

# Upgrading MCP Connector to Version 1.5

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

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

<table><colgroup><col> <col></colgroup><thead><tr><th>From Version</th><th>To Version</th></tr></thead><tbody><tr><td><div><div><p>1.0</p></div></div></td><td><div><div><p>1.x</p></div></div></td></tr></tbody></table>

## 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.

- The connector now includes the new `MCP:SCHEMA_VALIDATION_FAILED` 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. This parameter lets you 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](#remove-property).

- 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:

```xml
<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

- [MCP Connector Reference](https://docs.mulesoft.com/mcp-connector/1.5/mcp-connector-reference)

- [MCP Connector Examples](https://docs.mulesoft.com/mcp-connector/1.5/mcp-connector-examples)

- [Introduction to Anypoint Connectors](https://docs.mulesoft.com/connectors/introduction/introduction-to-anypoint-connectors)

- [MuleSoft Help Center](https://help.mulesoft.com)