Using Anypoint Code Builder to Configure MCP Connector 1.1 | MuleSoft Documentation
# Using Anypoint Code Builder to Configure MCP Connector 1.1
**Open Beta Release** : The **cloud IDE is in open beta**. Any use of Anypoint Code Builder in its beta state is subject to the applicable beta services terms and conditions, available from the IDE.
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
  * 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.
  2. From **Quick Actions** , click **Develop an Integration** :
  3. Complete the following in the **Develop an Integration** form:
Attribute | Value  
---|---  
**Project Name** |  Unique name for your project. 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 `salesforce-integration`.  
**Project Location** |  Your home directory or another directory you create. Click **Browse** to select a different directory for the integration project. Don’t create the project within another project directory. See Adding Folders to Your Home Directory.  
  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 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 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.
    2. In the **Add Component** panel, click **Connectors**.
    3. Click the connector name and then click the operation to add, such as **Publish** :
If the connector is not available locally, click the (**Search in Exchange**) toggle:
Search locally  
---  
Search in Exchange  
    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 the 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.
  5. Select the **Advanced** tab to configure the following attributes:
Attribute | Description | Required  
---|---|---  
Allowed methods | To allow all HTTP methods (default), do not define this attribute. To restrict certain methods, specify all allowed HTTP methods, for example, `GET, POST`, as a comma-separated list.  
Response streaming mode | Whether to use streaming when the response is sent.  
Output MIME type | MIME type of the payload that this component outputs.  
Parameters | Appends a key-value pair for a reader property to the value of the Output MIME attribute. Multiple key-value pairs are allowed.  
Output encoding | Encoding of the payload that this component outputs.  
Streaming Strategy | Configures the way data streams are consumed in Mule apps.  
Primary node only | Select this option to execute the **Listener** trigger on the primary node only when running in a cluster.  
Redelivery policy | Configures the redelivery policy for executing requests that generate errors. You can add a redelivery policy to any source in a flow.  
Reconnection strategy | 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.  
Response | See HTTP Response Attributes.  
Error Response | HTTP error response returns a status code for the error.  
Body of the error message.  
Headers to include in the error message.  
Status code | Status code of the error response, for example, `500`.  
Reason phrase | Reason for the error, for example, `Gateway Timeout` or `Internal Server Error`.  


## Add Components 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:
  3. Change the name of the flow:
    1. Click **Flow**.
    2. Click the edit icon.
    3. Enter the flow name, and click the checkmark.
    4. In the canvas UI, click the (**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:
The configuration XML file now includes the XML for the HTTP Listener into the `<flow/>` element, for example:
```
<flow name="getFlights" >
 <http:listener path="" config-ref="" doc:name="Listener" doc:id="ojzfry" />
</flow>
```



## Configure the Component Attributes
After you add components to your integration project, configure the attributes in the component UI, or configure the attributes directly in the XML code editor.
Connector XML tags start with a namespace followed by an operation, following the syntax `namespace:operation`, such as `<db:select/>` for a **Select** operation in Anypoint Connector for Database (Database Connector).
You can use autocomplete from an expression (**fx**) field for a component to select DataWeave functions from the Core module and other values accepted in this field.
## 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 (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** :
This command adds the following code to the file:
```
<?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.
## 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.
## See Also
  * Anypoint Code Builder Overview
  *   * Using Anypoint Code Builder to Configure a Connector
  * Defining and Securing Properties for a Mule Application
  * Triggering Flows in Your Development Environment
  * Working with Code Snippets
  * Debugging Mule Applications
  * MuleSoft Help Center