--- schema_version: "1" id: 2e4b5ec5b0ff149551d6d1c348364ade043aa26130c54d787dc9da3e7c9d4af7 title: Releasing Connectors collection: mulesoft version: current locale: en-us portal_url: https://docs.salesforce.com/mulesoft/current/en-us/connector-builder/releasing-connectors.md canonical_url: https://docs.mulesoft.com/connector-builder/releasing-connectors source_site: docs.mulesoft.com content_type: documentation content_hash: 1b79443d9b0233bc90d632fb5d72a9887552528ff41ceb321e8e3f0137a9cfa8 description: MuleSoft Documentation Site latest: true --- --- product: Connector Builder version: master --- # Releasing Connectors > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Learn how to release your connector. Releasing is the process of making your connector available to others. Connector Builder supports releasing your connector to Anypoint Platform and to Salesforce Flow. ## Release Connectors to Anypoint Platform To make your connector available on Anypoint Platform, release it to Anypoint Exchange. Connector Builder supports private releases to Anypoint Exchange only. The connector can still be shared with other accounts or teams. After you release your connector, you should see your published connector in Anypoint Exchange. If you’re unable to see the published connector, click **Back to legacy search** to switch the search mode. For more information about publishing to Exchange, see [Publishing Assets Using Maven](https://docs.mulesoft.com/exchange/to-publish-assets-maven). ### Release Connectors to Anypoint Platform Using the UI 1. Open your IDE and go to **Connector Builder - Editor**. 2. Click **Publish…​**. 3. In the UI, complete all checklist items to ensure you meet the release requirements. 4. Click **Publish to Anypoint Exchange**. This runs `mvn deploy` from the `{projectname}-anypoint-connector-model` directory. ### Release Connectors to Anypoint Platform with MCP Tools (Cursor) 1. Open the Connector Builder extension in Cursor. 2. Select **Settings** and ensure **Enable Mcp Tools** is enabled. 3. Open the Cursor chat window (if not already open). 4. Ask the agent to release the connector. For example, enter `Publish this connector to Anypoint Exchange`. This calls the `uc_connector_lifecycle` MCP tool with `type='publish'`, which releases the connector to Anypoint Exchange. The same tool with `type='build'` builds the connector locally. 5. Enter the required inputs when prompted. 6. Confirm your inputs. Connector Builder releases the connector to Anypoint Exchange. For more information, see [MuleSoft DX MCP Server Tool Reference](https://docs.mulesoft.com/mulesoft-mcp-server/reference-mcp-tools). ## Release Connectors to Salesforce Flow You can deliver a custom Flow connector in two ways: - Publish to AgentExchange as a standalone connector listing Package the connector as its own managed 2GP solution. Submit the AgentExchange Security Review. Then list it publicly on AgentExchange, or distribute it privately by sharing a direct package URL. - Deploy to a single customer org A Salesforce customer can build a custom connector and deploy it directly to their own org. No AgentExchange listing is required. In both cases, the connector runs in the customer org and requires the MuleSoft for Flow add-on. Each connector operation consumes Automation Credits. ### Release Connectors to AgentExchange 1. Package Your Connector as a Standalone Managed 2GP Solution Package your custom connector as a standalone 2GP managed package, one package per connector, with no other app content. This is the format AgentExchange requires for distribution and installation in subscriber orgs. For more information, see [Package a Custom Flow Connector as a 2GP Managed Package](https://developer.salesforce.com/docs/atlas.en-us.pkg2_dev.meta/pkg2_dev/dev2gp_package_custom_flow_connector.htm). 2. Check Listing Readiness Before submitting your custom Flow connector for security review, verify that your package version is ready to be listed. For more information, see [Security Requirements for AppExchange Partners and Solutions](https://developer.salesforce.com/docs/atlas.en-us.packagingGuide.meta/packagingGuide/security_review_create_secure_solution.htm). 3. Pass the AgentExchange Security Review Your custom Flow connector must pass the AgentExchange Security Review before it gets listed on AgentExchange. This applies to both public AgentExchange listings and private listings distributed by direct package URL. For more information, see [Pass the AgentExchange Security Review](https://developer.salesforce.com/docs/atlas.en-us.packagingGuide.meta/packagingGuide/security_review_guidelines.htm). 4. Create and Publish Your AgentExchange Listing After your custom connector package passes security review, create the listing in Partner Console. For more information, see [Manage Your AppExchange Listings](https://developer.salesforce.com/docs/atlas.en-us.packagingGuide.meta/packagingGuide/packaging_distributing.htm). 5. Maintain and Update Your Connector If you revise a published custom connector, update your AppExchange listing so that customers get access to the latest version. For more information, see [Manage Your Published Listings](https://developer.salesforce.com/docs/atlas.en-us.packagingGuide.meta/packagingGuide/appexchange_manage_published_listings_intro.htm). ### Release Connectors Directly to a Salesforce Org To deploy a Flow connector directly to a Salesforce org, deploy the connector JAR as an `IntegArtifactDef` metadata component using Salesforce CLI. This is the Flow connector JAR produced from [Packaging Connectors](https://docs.mulesoft.com/connector-builder/packaging-connectors). The JAR file name follows the pattern `{projectname}-flow-connector-model-{version}-dw-library.jar`. 1. Log in to your org from Salesforce CLI: sf org login web -r > [!NOTE] Lightning URLs are not supported. 2. Generate a Salesforce project to host the connector metadata: sf project generate --output-dir my-workspace --name my-project 3. In `my-workspace/my-project/sfdx-project.json`, set `"sourceApiVersion": "66.0"`. 4. Inside the project folder, create a folder for the connector under `force-app/main/default/integArtifactDefs/`: mkdir -p force-app/main/default/integArtifactDefs// 5. Inside that folder, create a `-meta.xml` file: ```xml {description} {displayName} {groupId} ``` 6. Create a versioned subfolder for the connector JAR and place the JAR inside it: mkdir -p force-app/main/default/integArtifactDefs/// 7. Deploy the connector to the org: sf project deploy start -m "IntegArtifactDef:" --target-org