---
schema_version: "1"
id: 8a3ca6bdb1542b2cfd21b9aa00b7b6e782da24371529ad4c9fae24262454c337
title: Using Anypoint Code Builder to Configure MCP Connector 1.3
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/mcp-connector/1.3/mcp-connector-acb.md
canonical_url: https://docs.mulesoft.com/mcp-connector/1.3/mcp-connector-acb
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 2fadda05dd0e6220cfaf637668c0727eb9452849e824a6e62a0f2b6767a5b401
description: MuleSoft Documentation Site
release: "1.3"
latest: false
---
---
product: MCP Connector
version: 1.3
---

# Using Anypoint Code Builder to Configure MCP Connector 1.3

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

Cloud IDE (Beta) is scheduled for retirement on August 31, 2026. August 30, 2026 is the last day you
can access Cloud IDE (Beta). Download your projects to work from Desktop IDE. Learn more in
[Migrate a Project from Cloud IDE to Desktop IDE](https://docs.mulesoft.com/anypoint-code-builder/int-import-mule-project#migrate-cloud-to-desktop).

To use Anypoint Code Builder to configure a connector or module, create a basic integration project
in Anypoint Code Builder, add connectors and other components to your Mule application to process
your business logic, and configure the attributes.

## Before You Begin

Before creating an integration project, you must:

- [Set up and access the Anypoint Code Builder web or desktop IDE](https://docs.mulesoft.com/anypoint-code-builder/start-acb)

- Have credentials to access the connector’s API

- Ensure that the Visual Studio Code Extension Pack for Java is installed.

To use this connector, you must be familiar with:

- The connector’s API

- Anypoint Connectors

- Mule runtime engine (Mule)

## Create a New Integration Project

To create a new integration project:

1.  In the activity bar of the IDE, click the
    ![Anypoint Code Builder icon](/mulesoft/current/en-us/connectors/_images/acb-icon-ms-logo.png) (**Anypoint Code
    Builder**) icon.

2.  From **Quick Actions**, click **Develop an Integration**:

    ![Develop an Integration link highlighted in the Getting started section](/mulesoft/current/en-us/anypoint-code-builder/_images/develop-integration-option-mat.png)

3.  Complete the following in the **Develop an Integration** form:

    <table><colgroup><col> <col></colgroup><thead><tr><th>Attribute</th><th>Value</th></tr></thead><tbody><tr><td><div><div><p><strong>Project Name</strong></p></div></div></td><td><div><div><p>Unique name for your project.</p></div><div><p>This name is used as the title and name of the integration project file. For example, if the project name is "Salesforce Integration," the project file name is <code>salesforce-integration</code>.</p></div></div></td></tr><tr><td><div><div><p><strong>Project Location</strong></p></div></div></td><td><div><div><p>Your home directory or another directory you create. Click <strong>Browse</strong> to select a different directory for the integration project.</p></div><div><p>Don’t create the project within another project directory.</p></div><div><p>See <a href="https://docs.mulesoft.com/anypoint-code-builder/start-add-folders">Adding Folders to Your Home Directory</a>.</p></div></div></td></tr></tbody></table>

4.  Select the type of project to create by selecting either the **Empty Project** or **Template or
    Example** card.

5.  Select the **Mule runtime** and **Java Version** for your app.

6.  Click **Create Project**.

## Add the Connector to Your Integration Project

Anypoint Connectors provide operations for retrieving, modifying, and sending data to and from
systems.

In addition to the
[built-in connectors](https://docs.mulesoft.com/anypoint-code-builder/acb-reference#builtin-connectors) that Anypoint
Code Builder provides, you can download many other connectors from Anypoint Exchange.

To import a connector from Exchange and add it to your configuration:

1.  In the Explorer view, open the configuration XML file for your project, such as
    `my-project-name.xml`.

2.  Click the
    ![Show Mule graphical mode icon](/mulesoft/current/en-us/anypoint-code-builder/_images/icon-tree-view.png) (**Show
    Mule graphical mode**) icon in the activity bar to open the canvas UI if it doesn’t open
    automatically.

3.  Add the connector the same way you added other components from the canvas UI:

    1.  In the canvas UI, click the
        ![Add component icon](/mulesoft/current/en-us/anypoint-code-builder/_images/icon-plus.png) (**Add component**)
        icon.

    2.  In the **Add Component** panel, click **Connectors**.

    3.  Click the connector name and then click the operation to add, such as **Publish**:

        ![Add Publish operation from Anypoint MQ Connector](/mulesoft/current/en-us/anypoint-code-builder/_images/int-add-connector-operation.png)

        If the connector is not available locally, click the
        ![Search in Exchange icon](/mulesoft/current/en-us/anypoint-code-builder/_images/icon-search-exchange.png)
        (**Search in Exchange**) toggle:

        ![Search in Exchange toggle](/mulesoft/current/en-us/anypoint-code-builder/_images/int-connector-search-exchange.png)

        <table><tbody><tr><td><i data-value="1"></i><b>1</b></td><td>Search locally</td></tr><tr><td><i data-value="2"></i><b>2</b></td><td>Search in Exchange</td></tr></tbody></table>

    4.  Select the connector to add to your project.

    5.  Select the operation from the **Add Component** panel.

Adding a connector to an integration project does not make that connector available to other
projects in your Anypoint Code Builder workspace.

## Configure a Source For the Flow

A trigger (source) starts the flow when specified conditions are met. If a connector has its own
associated sources, you can use a connector-specific trigger to initiate the flow. Each connector
trigger has a unique configuration.

You can configure the following sources for this connector:

- **HTTP > Listener**

  Initiates a flow each time it receives a request on the configured host and port

- **Scheduler**

  Initiates a flow when a time-based condition is met

For example, to configure an HTTP Listener trigger, follow these steps:

1.  Click the **Listener** component on the canvas UI.

2.  (Optional) Click the edit icon to change the name of the **Listener** component.

3.  (Optional) If you created a configuration file for the connector, select it.

4.  In the **General** tab, in the **Path** field, enter the relative path for the path set in the
    HTTP configuration element. See
    [Configure Paths](https://docs.mulesoft.com/http-connector/latest/http-listener-ref#configure-paths).

5.  Select the **Advanced** tab to configure the following attributes:

    <table><colgroup><col> <col> <col></colgroup><thead><tr><th>Attribute</th><th>Description</th><th>Required</th></tr></thead><tbody><tr><td><p>Allowed methods</p></td><td><p>To allow all HTTP methods (default), do not define this attribute. To restrict certain methods, specify all allowed HTTP methods, for example, <code>GET, POST</code>, as a comma-separated list.</p></td><td><p>No</p></td></tr><tr><td><p>Response streaming mode</p></td><td><p>Whether to use streaming when the response is sent.</p></td><td><p>No</p></td></tr><tr><td><p>Output MIME type</p></td><td><p>MIME type of the payload that this component outputs.</p></td><td><p>No</p></td></tr><tr><td><p>Parameters</p></td><td><p>Appends a key-value pair for a reader property to the value of the Output MIME attribute. Multiple key-value pairs are allowed.</p></td><td><p>No</p></td></tr><tr><td><p>Output encoding</p></td><td><p>Encoding of the payload that this component outputs.</p></td><td><p>No</p></td></tr><tr><td><p>Streaming Strategy</p></td><td><p>Configures the way data streams are consumed in Mule apps.</p></td><td><p>No</p></td></tr><tr><td><p>Primary node only</p></td><td><p>Select this option to execute the <strong>Listener</strong> trigger on the primary node only when running in a cluster.</p></td><td><p>No</p></td></tr><tr><td><p>Redelivery policy</p></td><td><p>Configures the redelivery policy for executing requests that generate errors. You can add a redelivery policy to any source in a flow.</p></td><td><p>No</p></td></tr><tr><td><p>Reconnection strategy</p></td><td><p>When an operation in a Mule application fails to connect to an external server, the default behavior is for the operation to fail immediately and return a connectivity error. You can modify the default behavior by configuring the reconnection strategy for the operation.</p></td><td><p>No</p></td></tr><tr><td><p>Response</p></td><td><p>See <a href="https://docs.mulesoft.com/http-connector/latest/http-documentation#HttpResponseAttributes">HTTP Response Attributes</a>.</p></td><td><p>No</p></td></tr><tr><td><p>Error Response</p></td><td><p>HTTP error response returns a status code for the error.</p></td><td><p>No</p></td></tr><tr><td><p>Body</p></td><td><p>Body of the error message.</p></td><td><p>No</p></td></tr><tr><td><p>Headers</p></td><td><p>Headers to include in the error message.</p></td><td><p>No</p></td></tr><tr><td><p>Status code</p></td><td><p>Status code of the error response, for example, <code>500</code>.</p></td><td><p>No</p></td></tr><tr><td><p>Reason phrase</p></td><td><p>Reason for the error, for example, <code>Gateway Timeout</code> or <code>Internal Server Error</code>.</p></td><td><p>No</p></td></tr></tbody></table>

For complete source configuration details, see the
[MCP Connector Reference](https://docs.mulesoft.com/mcp-connector/1.3/mcp-connector-reference).

### Example: Configure a Tool Listener Source

A common use case is exposing operations as tools that MCP clients can invoke. In the XML editor,
add a **Tool Listener** source to your flow:

```xml
<flow name="my-tool-flow">
    <mcp:tool-listener
        config-ref="MCP_Server_Config"
        name="get-user-info">
        <mcp:description><![CDATA[Retrieves user information by ID]]></mcp:description>
        <mcp:parameters-schema><![CDATA[{
            "type": "object",
            "properties": {
                "userId": {"type": "string"}
            },
            "required": ["userId"]
        }]]></mcp:parameters-schema>
    </mcp:tool-listener>
</flow>
```

## Configure an MCP Connection

MCP Connector supports both client and server configurations with different connection types.

### Configure an MCP Client Connection

Use client configurations to connect your Mule application to external MCP servers.

#### Streamable HTTP Client

The Streamable HTTP client connection enables load-balanced, scalable connections to MCP servers:

```xml
<mcp:client-config name="MCP_Client_Config" clientName="MCP Client" clientVersion="1.0.0">
    <mcp:streamable-http-client-connection
        serverUrl="https://mcp-server.example.com"
        mcpEndpointPath="/mcp"
        requestTimeout="30"
        requestTimeoutUnit="SECONDS">
        <mcp:default-request-headers>
            <mcp:default-request-header key="Authorization" value="Bearer ${api.token}"/>
        </mcp:default-request-headers>
    </mcp:streamable-http-client-connection>
</mcp:client-config>
```

#### SSE Client Connection (Deprecated)

The SSE (Server-Sent Events) client enables persistent, server-push connections:

```xml
<mcp:client-config name="MCP_SSE_Client_Config">
    <mcp:sse-client-connection
        serverUrl="https://mcp-server.example.com"
        sseEndpointPath="/sse"
        requestTimeout="30"
        reconnectionDelay="500"
        reconnectionDelayUnit="MILLISECONDS">
    </mcp:sse-client-connection>
</mcp:client-config>
```

### Configure an MCP Server Connection

Use server configurations to expose your Mule application as an MCP server.

#### Streamable HTTP Server

```xml
<http:listener-config name="HTTP_Listener_Config">
    <http:listener-connection host="0.0.0.0" port="8081"/>
</http:listener-config>

<mcp:server-config name="MCP_Server_Config"
    serverName="My MCP Server"
    serverVersion="1.0.0">
    <mcp:streamable-http-server-connection
        listenerConfig="HTTP_Listener_Config"
        mcpEndpointPath="/mcp"
        requestTimeout="10"
        requestTimeoutUnit="SECONDS">
    </mcp:streamable-http-server-connection>
</mcp:server-config>
```

#### SSE Server Connection (Deprecated)

```xml
<http:listener-config name="HTTP_Listener_Config">
    <http:listener-connection host="0.0.0.0" port="8081"/>
</http:listener-config>

<mcp:server-config name="MCP_Server_Config"
    serverName="My MCP Server"
    serverVersion="1.0.0">
    <mcp:sse-server-connection
        listenerConfig="HTTP_Listener_Config"
        sseEndpointPath="/sse"
        messagesPath="/message"
        requestTimeout="10"
        requestTimeoutUnit="SECONDS">
    </mcp:sse-server-connection>
</mcp:server-config>
```

## Configure Authentication

MCP Connector client connections support standard HTTP authentication methods including Basic,
Digest, NTLM, and OAuth. For detailed authentication and security configuration, see
[Applying Security to the MCP Server](https://docs.mulesoft.com/mcp-connector/1.3/mcp-connector-config-topics).

## Add Operations to Your Project

Add components to your integration project to build a flow:

1.  In the **Explorer** view, open the XML file for your project, such as `my-project-name.xml`.

2.  Select **Build a Flow** from the start card to create an empty flow:

    ![Anypoint Code Builder canvas with starting cards with the options to start from scratch, build a flow, or build a subflow](/mulesoft/current/en-us/connectors/_images/acb-build-flow.png)

3.  Change the name of the flow:

    1.  Click **Flow**.

    2.  Click the edit icon.

        ![Arrow pointing to the flow name edit pencil icon](/mulesoft/current/en-us/connectors/_images/acb-change-flow-name.png)

    3.  Enter the flow name, and click the checkmark.

    4.  In the canvas UI, click the
        ![Add component icon](/mulesoft/current/en-us/anypoint-code-builder/_images/icon-plus.png) (**Add component**)
        icon.

    5.  In the **Add Component** panel, search for and select your component from the results. The
        following example shows the **Listener** component from the **HTTP** search results:

        ![Listener component highlighted in the Add Component section](/mulesoft/current/en-us/anypoint-code-builder/_images/main-tutorial-add-first-listener.png)

        The configuration XML file now includes the XML for the HTTP Listener into the `<flow/>`
        element, for example:

        ```XML
        <flow name="getFlights" >
          <http:listener path="" config-ref="" doc:name="Listener" doc:id="ojzfry" />
        </flow>
        ```

For a complete list of operations and their configurations, see
[Supported Operations](https://docs.mulesoft.com/mcp-connector/1.3/mcp-connector-reference#supported-operations).

### Example: Using Operations

After you configure a connection, you can add operations to interact with MCP servers (when
configured as a client) or handle requests (when configured as a server).

Example of calling a tool on an MCP server:

```xml
<mcp:call-tool config-ref="MCP_Client_Config" name="get-user-info">
    <mcp:arguments><![CDATA[#[{
        "userId": payload.userId
    }]]]></mcp:arguments>
</mcp:call-tool>
```

Example of reading a resource from an MCP server:

```xml
<mcp:read-resource config-ref="MCP_Client_Config" uri="file:///documents/report.txt"/>
```

For detailed information on each operation’s parameters and usage, see the
[MCP Connector Reference](https://docs.mulesoft.com/mcp-connector/1.3/mcp-connector-reference).

## Configure TLS for Secure Connections

To secure connections with TLS:

```xml
<tls:context name="TLS_Context">
    <tls:trust-store
        path="truststore.jks"
        password="${tls.truststore.password}"/>
    <tls:key-store
        path="keystore.jks"
        password="${tls.keystore.password}"
        keyPassword="${tls.key.password}"/>
</tls:context>

<mcp:client-config name="MCP_Client_Config">
    <mcp:streamable-http-client-connection
        serverUrl="https://secure-mcp-server.example.com"
        tlsContext="TLS_Context">
    </mcp:streamable-http-client-connection>
</mcp:client-config>
```

## Create a New Configuration XML File

Anypoint Code Builder creates the initial Mule configuration XML file in `src/main/mule` within the
Mule project. This file contains global configurations and flow structures.

You can create additional configuration files, for example, to store global configurations.

To create a new XML configuration file:

1.  In the Explorer view, right-click the **mule** folder (`src/main/mule`) and select **New File**.

    Alternatively, use the menu.

    Show me how

    Select the `mule` folder, and then:

    - In the desktop IDE, select **File** > **New Mule Configuration File**.

    - In the cloud IDE, click the ![](/mulesoft/current/en-us/anypoint-code-builder/_images/icon-menu.png) (menu)
      icon, and select **File** > **New File**.

2.  Enter a name for the new file with the `.xml` extension.

3.  In the Editor view for the new file, press Ctrl+Space to display available options.

4.  Select **Empty mule configuration**:

    ![New Mule configuration option in auto-correct](/mulesoft/current/en-us/anypoint-code-builder/_images/int-new-mule-config.png)

    This command adds the following code to the file:

    ```xml
    <?xml version="1.0" encoding="UTF-8"?>
    <mule xmlns="http://www.mulesoft.org/schema/mule/core" xmlns:doc="http://www.mulesoft.org/schema/mule/documentation"
        xmlns:ee="http://www.mulesoft.org/schema/mule/ee/core"
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xsi:schemaLocation="http://www.mulesoft.org/schema/mule/core http://www.mulesoft.org/schema/mule/core/current/mule.xsd
        http://www.mulesoft.org/schema/mule/ee/core http://www.mulesoft.org/schema/mule/ee/core/current/mule-ee.xsd">

    </mule>
    ```

## Debug the App

Debug your Mule application using the embedded debugger in Anypoint Code Builder.

See [Debugging Mule Applications](https://docs.mulesoft.com/anypoint-code-builder/int-debug-mule-apps).

## Deploy the App

These are available for deployment:

- CloudHub 2.0

- Runtime Fabric

- Hybrid

- CloudHub (with limitations, such as you can’t apply policies)

For more information about deploying apps, see
[Deployment Options](https://docs.mulesoft.com/runtime-manager/deployment-strategies).

## See Also

- [Anypoint Code Builder Overview](https://docs.mulesoft.com/anypoint-code-builder/)

- [Creating Integrations](https://docs.mulesoft.com/anypoint-code-builder/int-create-integrations)

- [Using Anypoint Code Builder to Configure a Connector](https://docs.mulesoft.com/connectors/introduction/intro-config-use-acb)

- [Anypoint Code Builder Components and Commands Reference](https://docs.mulesoft.com/anypoint-code-builder/acb-reference)

- [Defining and Securing Properties for a Mule Application](https://docs.mulesoft.com/anypoint-code-builder/int-create-secure-configs)

- [Triggering Flows in Your Development Environment](https://docs.mulesoft.com/anypoint-code-builder/int-trigger-flows)

- [Configuring Components](https://docs.mulesoft.com/anypoint-code-builder/int-configure-components)

- [Debugging Mule Applications](https://docs.mulesoft.com/anypoint-code-builder/int-debug-mule-apps)

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