--- schema_version: "1" id: 94aa92382769635354cd613808892f43c0e6286c670bfa1a95cbe37065ecb507 title: Developing Integrations Using MuleSoft Vibes collection: mulesoft version: current locale: en-us portal_url: https://docs.salesforce.com/mulesoft/current/en-us/anypoint-code-builder/int-ai-developing-integrations.md canonical_url: https://docs.mulesoft.com/anypoint-code-builder/int-ai-developing-integrations source_site: docs.mulesoft.com content_type: documentation content_hash: def05694c2958ebf0bc6714996edd35029203f33149910df82bb5697073f5d41 description: MuleSoft Documentation Site latest: true --- --- product: Anypoint Code Builder version: master --- # Developing Integrations Using MuleSoft Vibes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt MuleSoft Vibes is a purpose-built assistant for the development lifecycle, available with Anypoint Code Builder. Use it to develop, manage, or maintain your applications. MuleSoft Vibes integrates with the [MuleSoft MCP Server](https://docs.mulesoft.com/mulesoft-mcp-server/) and supports many capabilities, such as: - Developing API specifications - Creating and configuring applications - Searching for assets - Deploying and managing instances - Managing custom metadata All of these actions are driven by natural language messages. When you generate an integration, MuleSoft Vibes transforms your business logic into a Mule application. The generated application includes: - Flows - Connector configurations - A sample `config.properties` file - Dependencies required for connectors, such as Salesforce and HTTP These capabilities are powered by large language models (LLMs) that run within the Salesforce Shared Trust Boundary. > [!NOTE] MuleSoft Vibes is available on US, EU, Canada, Japan, India, Australia, and United Kingdom > cloud hosts. ## Before You Begin Before you start creating your API spec, make sure you meet the following prerequisites: - [Set up and access Anypoint Code Builder](https://docs.mulesoft.com/anypoint-code-builder/start-acb). - Make sure you have the [required Anypoint Code Builder permissions](https://docs.mulesoft.com/anypoint-code-builder/start-configure-permissions#permissions). - Ensure you have the following permissions to use MuleSoft Vibes: - **Mule Developer Generative AI User** - Make sure Einstein is enabled in Access Management. For more information, see [Enabling Einstein for Anypoint Platform](https://docs.mulesoft.com/access-management/enabling-generative-ai). > [!NOTE] MuleSoft Vibes always uses the permissions of the Anypoint Platform user who is logged > into Anypoint Code Builder, and can only execute actions that the authenticated user has > permission to perform in Anypoint Platform. ## Unified MuleSoft Vibes Experience MuleSoft Vibes provides a single panel where you can develop integrations and API specifications. Unlike earlier versions of generative features, it does not insert output through a separate panel. Instead, it writes directly into your project files when you grant edit permissions. Depending on your settings, MuleSoft Vibes can: - Request approval before writing to your files. - Write automatically if **Auto-approve** is enabled in the MuleSoft Vibes settings. For details on configuring permissions and server connections, see [Troubleshooting AI Features in Anypoint Code Builder](https://docs.mulesoft.com/anypoint-code-builder/troubleshoot-generative-ai). ## Provide Additional Context You can improve the accuracy of generated outputs by adding extra context to MuleSoft Vibes. Besides the message you send in the panel, you can attach these types of input: - **Files** – Add a requirements file or other reference documents. - **Folders** – Provide an entire project folder for MuleSoft Vibes to consider. - **Terminal Input** – Share terminal outputs as context for the request. This context helps MuleSoft Vibes generate flows and API specifications that align more closely with your requirements. ## Trust Layer The Einstein trust layer bridges Anypoint Platform and the LLMs, as shown in this flow: ![Flow depicting how the trust layer works, including the steps of the flow](/mulesoft/current/en-us/anypoint-code-builder/_images/acb-einstein-trust-layer.png)
1You create a message based on your use case and send it to MuleSoft Vibes.
2To minimize inaccurate responses, messages are grounded with MuleSoft proprietary data and user context.
3To ensure safe data transfer to external LLMs, the message is sent via a secure gateway.
4All data remains within Salesforce-managed boundaries.
5After the LLM generates a response, the content is returned through the secure gateway.
6MuleSoft validates the generated output to ensure compatibility with the MuleSoft ecosystem.
7Anypoint Code Builder logs the interaction for monitoring before surfacing the validated response.
> [!IMPORTANT] This feature uses AI models that can produce inaccurate or harmful responses. Review > the generated output for accuracy and safety before using it. You assume responsibility for the > output when making business decisions. ## See Also - [Troubleshooting](https://docs.mulesoft.com/anypoint-code-builder/troubleshooting) - [Creating API Specs with MuleSoft Vibes](https://docs.mulesoft.com/anypoint-code-builder/vibes-api-ai-create-spec) - [Custom metadata in MuleSoft Vibes](https://docs.mulesoft.com/anypoint-code-builder/int-manage-custom-metadata#custom-metadata-vibes)