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

# Upgrading MCP Connector to Version 1.1

> 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.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.1/mcp-connector-reference)

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

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

- [Salesforce Help](https://help.salesforce.com)