Salesforce Docs Portal

Getting Started with Anypoint Code Builder

Anypoint Code Builder is built from the Anypoint Extension Pack for Visual Studio Code. You must load the extension pack to your local Visual Studio Code installation.

Set up Anypoint Code Builder

The extensions in Anypoint Extension Pack are available from the Visual Studio Marketplace.

Before You Begin Anypoint Code Builder Setup

Before installing the Anypoint Code Builder extensions to VS Code, make sure you have an Anypoint Platform account with the required permissions:

  • An administrator with an Anypoint Platform organization account must provide you with the necessary permissions. See Configuring Permissions.

  • Anypoint Platform requires a user account. You can use an existing account or create one from Anypoint Platform (see supported Cloud Hosts).

For information about OS and system compatibility, see Anypoint Code Builder Release Notes.

Hardware and Storage Requirements

Anypoint Code Builder relies on Visual Studio Code (VS Code), Java, Node.js, Maven, and local build artifacts. To avoid timeouts, slow dependency resolution, and poor responsiveness, your environment must meet the following minimum specifications. Recommended values improve performance for larger workspaces and frequent local runs.

For supported operating systems and extension compatibility, see Anypoint Code Builder Release Notes.

To check whether your machine meets these specifications and apply available optimizations automatically, ask MuleSoft Vibes or Claude Code to run the run-system-diagnostics skill.

Hardware Requirements

Component Minimum Recommended

CPU

8 cores or 8 vCPUs

More cores for parallel builds and multiple large projects

RAM

32 GB

Additional memory for multiple VS Code windows and heavy local testing

Primary storage type

NVMe SSD (PCIe 3.0 or higher)

Same; avoid network-only or heavily virtualized disks for the OS, user profile, and project roots

Free disk space

50 GB

100 GB

Network

1 Gbps

10 Gbps (for large dependency downloads and corporate artifact repositories)

Storage Performance

Local disks that can’t sustain the following metrics often show slow indexing, Maven repository access, and Mule application startup.

Confirm values with your storage vendor or disk benchmark tooling on the volume that hosts your user profile, local Maven repository, VS Code data, and project directories. Consider input/output operations per second (IOPS) as well; higher IOPS generally improve responsiveness for random small-file access.

Metric Minimum Requirement

Random read IOPS (4 KB)

10,000 IOPS

Random write IOPS (4 KB)

8,000 IOPS

Sequential read

1,250 MB/s

Sequential write

1,000 MB/s

Antivirus, endpoint detection, and real-time scanning can reduce read and write speeds below these minimums. To reduce this impact, configure antivirus and endpoint protection exclusions.

Configure Antivirus and Endpoint Protection Exclusions

On managed devices, add exclusions for the processes and directories that Anypoint Code Builder and its toolchain use most intensively. Exclusions reduce file locking, false positives, and severe I/O latency during builds. Your organization’s security policy decides whether exclusions are allowed, so use the list with your security team.

For the full list of processes and directories to exclude, see Antivirus Exclusion Paths.

Windows Performance

On Windows, avoid running projects from network-mapped drives, because remote file access adds latency to project loading and canvas responsiveness. Store projects on local storage that meets the requirements in Storage Performance, and keep Anypoint Extension Pack updated to the latest version to benefit from ongoing file read and write optimizations for Windows.

Power Settings

Power management can throttle CPU and disk performance during long builds or local runs.

  • Windows: Prefer a High performance or Balanced power plan while you work; avoid battery saver or aggressive power saving when the machine is on AC power.

  • macOS: On notebooks, reduce battery-focused throttling where your org allows it—for example, adjust System Settings under Battery or Energy when plugged in.

For more information about hardware and storage requirements, see Hardware and Storage Requirements.

Install, Update, or Uninstall Anypoint Extension Pack

Use of Anypoint Code Builder in VS Code on your computer requires the Anypoint Extension Pack.

Install Anypoint Extension Pack

To install the Anypoint Extension Pack into VS Code:

  1. Open VS Code.

  2. Find Anypoint Extension Pack from within VS Code or from Visual Studio Marketplace.

    To avoid installation errors:

    Do not install the individual Anypoint Code Builder extensions that are also available separately from Anypoint Extension Pack in Visual Studio Marketplace.

    • To install from within VS Code, launch the Extensions menu by clicking the Extensions icon from the activity bar or pressing Cmd+Shift+x (Mac) or Ctrl+Shift+x (Windows), and search for the extension pack.

      Select Install Release Version.

    • To install from the Visual Studio Marketplace website, find the extension pack, and install:

      Select Install Release Version.

      For additional guidance, see the Visual Studio Code website.

  3. Open the Extensions menu, and review the extensions in Anypoint Extension Pack:

    Anypoint Extension Pack contains these extensions:

    • Anypoint Code Builder - API Extension

    • Anypoint Code Builder - APIkit Extension

    • Anypoint Code Builder - DataWeave Extension

    • Anypoint Code Builder - Dependencies Extension

    • Anypoint Code Builder - Integration Extension

    • Anypoint Code Builder - MUnit Extension

    • Anypoint Code Builder - Platform Extension

      For versioning information about extensions in Anypoint Extension Pack, see the Change Log.

  4. Recommended: Ensure that the Anypoint extensions update automatically by right-clicking each extension to see if Auto Update All (From Publisher) is checked. If it’s not, select Auto Update for each extension, for example:

    Setting an extension to auto-update

    Ensure this option is checked.

  5. Click the MuleSoft icon in the activity bar to access and use Anypoint Code Builder features.

    MuleSoft icon for Anypoint Code Builder in the activity bar

  6. Confirm that the Anypoint Code Builder menu loads.

  7. Disable other VS Code extensions that you don’t need for Mule development.

    Java-based extensions, such as a Java Language Server, Java debugger, or Spring Boot tools, run background processes that compete with Anypoint Code Builder for the same JVM resources, which can slow down canvas loading, DataSense resolution, and debugging.

  8. If your Anypoint Platform account uses a control plane other than US Cloud, change the Mule: Control Plane setting.

    For guidance, see Set Anypoint Code Builder to a Different Control Plane.

  9. Follow the steps in Log in to Anypoint Platform.

    NOTE

    If an Anypoint Platform session is active in any of your browsers when you install Anypoint Extension Pack, the extension pack uses that session to sign in to Anypoint Platform. You can log out or sign in from the status bar.

Install Anypoint Extension Pack in Cursor, Trae, or Devin

Cursor, Trae, and Devin use the OpenVSX marketplace by default. Before you can search for and install Anypoint Extension Pack in these IDEs, configure Visual Studio Marketplace as the gallery service URL.

Anypoint Extension Pack is also compatible with Windsurf. See Configuring an MCP Server for more about using the Anypoint Extension Pack, including MuleSoft MCP Servers, across compatible IDEs.

  • Cursor

  • Trae

  • Devin

  1. Open Cursor.

  2. Go to Cursor > Preferences > VS Code Settings.

  3. Search for Extensions › Gallery: Service Url.

  4. Replace the existing value with this URL:

    https://marketplace.visualstudio.com/_apis/public/gallery

  5. Restart Cursor to apply the change.

  6. After restarting, search for Anypoint Extension Pack in the Extensions panel and install it.

  1. Open Trae.

  2. Go to TRAE > Settings.

  3. Search for Extension Market Url.

  4. Replace the existing value with this URL:

    https://marketplace.visualstudio.com/_apis/public/gallery

  5. Restart Trae to apply the change.

  6. After restarting, search for Anypoint Extension Pack in the Extensions panel and install it.

  1. Open Devin.

  2. Go to Devin > Devin Settings > Plugins.

  3. In the Marketplace extension gallery service URL field, replace the existing value with this URL:

    https://marketplace.visualstudio.com/_apis/public/gallery

  4. Restart Devin to apply the change.

  5. After restarting, search for Anypoint Extension Pack in the Extensions panel and install it.

Update Anypoint Extension Pack

If Anypoint Extension Pack is installed, update to the latest version of the extension pack by following VS Code instructions in Update an extension manually.

Uninstall Anypoint Extension Pack

Typically, it is unnecessary to uninstall the extension pack or individual Anypoint Code Builder extensions from VS Code. For example, you can update to a new version without uninstalling first.

If you decide to uninstall Anypoint Extension Pack, follow the same procedure that you use for other VS Code extensions. Uninstalling the extension pack also uninstalls the individual Anypoint Code Builder extensions that are bundled within the extension pack, such as the DataWeave and APIkit extensions.

To uninstall:

  1. Open VS Code.

  2. From the activity bar, open the Extensions panel.

  3. Find and select Anypoint Extension Pack.

  4. In the Anypoint Extension Pack tab that opens, click Uninstall.

  5. To remove the Anypoint Code Builder extensions from the Extensions panel, click Reload on one of the extensions.

For additional guidance, see the VS Code documentation, Manage extensions.

You can reinstall at any time.

Sign in to Anypoint Platform from Anypoint Code Builder

Some Anypoint Code Builder features require you to sign in directly to Anypoint Platform. Anypoint Code Builder prompts you when login is necessary and guides you through the login process. However, it is a good practice to sign in after opening MuleSoft features.

  • An administrator with an Anypoint Platform organization account must provide you with the necessary permissions. See Configuring Permissions.

  • Anypoint Platform requires a user account. You can use an existing account or create one from Anypoint Platform (see supported Cloud Hosts).

You can sign in from the status bar or through a command, and you can log out from the status bar:

Sign in to Anypoint Platform from the Status Bar

The status bar shows your login status:

  • Not logged in to Anypoint Platform indicates that you must sign in to perform tasks that require a connection to Anypoint Platform.

    Login status message in the status bar

    You can sign in by clicking this notification and following the prompts to sign in.

  • A link to your user name indicates that you are signed in.

    You can log out by clicking your user name and following the prompts.

Sign in to Anypoint Platform from the Command Palette

You can use the Command Palette to sign in to Anypoint Platform.

To sign in from the Command Palette:

  1. Open the Command Palette.

    Show me how

    • Use the keyboard shortcuts:

      • Mac: Cmd+Shift+p

      • Windows: Ctrl+Shift+p

    • Select View > Command Palette.

  2. Select the following command:

    MuleSoft: Login to Anypoint Platform
    Login command within the Command Palette

    You can type login and use the filter in the results to select the command you want.

  3. Select Allow when prompted to sign in to the platform.

    allow login to anypoint platform

    After logging you in, Anypoint Platform displays a You can close this page now message.

  4. To verify your login, ensure that <your-username> replaces Not logged in to Anypoint Platform.

Log Out from Anypoint Platform from Anypoint Code Builder

Log out by:

  1. Clicking your username in the status bar

  2. Clicking Yes when asked Logout from Anypoint?

Sign in to a Different Anypoint Platform Account from Anypoint Code Builder

To use a different Anypoint Platform user account:

  1. Log out from the status bar.

    For guidance, see Log Out from Anypoint Platform from Anypoint Code Builder.

  2. Sign in from the status bar.

    For more guidance, see Sign in to Anypoint Platform from the Status Bar.

Set Anypoint Code Builder to a Different Control Plane

In Anypoint Code Builder, you can change your Anypoint Platform control plane to one of these options:

  • US Cloud (default)

  • EU Cloud

  • Canada Cloud

  • Japan Cloud

  • India Cloud

  • Australia Cloud

  • United Kingdom Cloud

  • Private Cloud Edition

Anypoint Platform instances do not share user accounts, projects, or other data. For more information, see Cloud Hosts.

Starting with Anypoint Code Builder 1.28.0, you can select Private Cloud Edition to connect to a Private Cloud Edition (PCE) 4.3.0 or later control plane that your organization hosts.

To change the control plane:

  1. If an API specification is open in the Explorer panel, close the project to avoid a synchronization error when you switch clouds.

    • Click File > Close Folder.

  2. Open the Settings panel:

    Selecting the EU cloud from Anypoint Code Builder

    Show me how

    • From the Anypoint Code Builder panel, click the (gear) icon.

    • From the activity bar, click the (gear) icon, select Settings, and search for mule in the Settings tab.

    • Provide the command MuleSoft: Open ACB Settings in the Command Palette.

  3. Scroll to Mule: Control Plane.

  4. Select the desired control plane.

  5. If you select Private Cloud Edition, set Mule: Control Plane PCE Url to the URL of your PCE control plane, for example https://pce.example.com.

    Anypoint Code Builder uses this URL only when Private Cloud Edition is selected. Anypoint Code Builder imports custom SSL certificates for the PCE host automatically.

  6. Restart Anypoint Code Builder to load all your changes.

  7. Follow the steps in Sign in to Anypoint Platform from Anypoint Code Builder.

    If you selected Private Cloud Edition, sign in from the Command Palette with this command:

    MuleSoft: Login to Anypoint Platform

    The command opens the PCE sign-in page.

If you selected Private Cloud Edition, bundled Mule runtime versions are available, and you can add another Mule runtime version locally. See Add a Mule Runtime Version Locally.

Add a Mule Runtime Version Locally

Starting with Anypoint Code Builder 1.28.0, you can add a Mule runtime version that Anypoint Code Builder does not include. Copy the Mule runtime directory into the user-installed folder. Anypoint Code Builder lists that version when you create a project and in Project Properties.

Use this option when your environment requires a Mule runtime version that is not bundled with Anypoint Code Builder, such as a version for Private Cloud Edition (PCE). Bundled Mule runtime versions are also available when the control plane is Private Cloud Edition. See Bundled Mule Runtime Versions.

To add a Mule runtime version:

  1. Copy the Mule runtime directory into this folder:

    ${user.home}/AnypointCodeBuilder/runtimes/user-installed

    Create the user-installed folder if it does not exist.

  2. Create a project, or open Project Properties.

    The Mule runtime version appears in the Mule runtime version menu. See Select Mule and Java Versions for a Project.

Anypoint Code Builder does not validate that a Mule runtime version is compatible with your PCE environment. Confirm compatibility before you run or deploy your application.