Contact Us 1-800-596-4880

Getting Started with MuleSoft Platform MCP Server

Scan, discover, govern, and monitor APIs, agents, MCP servers, and LLMs across your entire IT landscape from a single AI-accessible interface. MuleSoft Platform MCP Server gives AI tools governed access to your infrastructure to accelerate production-ready AI deployment. Connect your IDE in minutes using any MCP-compatible client.

Create a Connected App

Follow the steps in Create a Connected App That Acts on the User’s Behalf to create a connected app.

Additionally, when prompted, add the following permission scopes. These scopes enable you to use specific MuleSoft Platform MCP Server tools.

When creating the connected app, be sure to select the Authorization Code and Refresh Token grant types.

Refer to the MuleSoft Platform MCP Server Tool Reference for details on all MuleSoft Platform MCP Server tools. Only tools listed in these tables require specific permission scopes.

Exchange

To…​ Required Permission Associated Tools

View and download assets within a business group.

Exchange Viewer

View, create, and download assets within a business group, including editing asset portal content in an existing asset version.

Exchange Contributor

API Manager

To…​ Required Permission Associated Tools

View API configurations and policies in the specified environment.

API Manager Environment Viewer

View, create, modify, and delete APIs in the specified environment.

API Manager Environment Admin

Anypoint Monitoring

To…​ Required Permission Associated Tools

View but not modify content in Anypoint Monitoring.

Monitoring Viewer

Governance

To…​ Required Permission Associated Tools

View reports.

Governance Viewer

Manage profiles and view reports.

Governance Administrator

Runtime Manager

To…​ Required Permission Associated Tools

Create applications in a specific environment.

Manage Application Data

General

To…​ Required Permission Associated Tools

View organization information.

organization_read (implicit)

Configure Your IDE

Configure Claude Desktop, Claude Code, ChatGPT, Cursor, Windsurf, or VS Code to work with MuleSoft Platform MCP Server. After you add the configuration, verify it by checking that the server has started in the MCP section of your IDE.

MuleSoft remote MCP servers currently only support manual client registration through app creation and do not support other client registration methods such as Dynamic Client Registration (DCR).

Available Client Connections

When configuring your AI tool, use the endpoint for your region.

Use /mcp, and fall back to /mcp/sse if the client does not connect.

Type

URL

US Prod

omni.mulesoft.com (alias) / us1.omni.mulesoft.com

EU Prod

eu1.omni.mulesoft.com

CA Prod

ca1.omni.mulesoft.com

JP Prod

jp1.omni.mulesoft.com

IN Prod

in1.omni.mulesoft.com

For more information about Anypoint Platform regions, see Control Plane Hosting Options.

Claude Desktop

In Claude Desktop:

  1. Click Customize > Connectors.

  2. Click the add (+) icon, and then click Add Custom Connector.

  3. Name the connection, and enter the Remote Universal URL, for example, https://omni.mulesoft.com/mcp.

  4. Enter the Client ID and Client Secret from your connected app.

In your connected app:

  1. Log in to Anypoint Platform, and open your connected app.

  2. In the Redirect URLs field, enter https://claude.ai/api/mcp/auth_callback.

  3. To apply changes, click Continue.

Download Claude Desktop.

Claude Code

In your terminal, run the following command, replacing <PORT> with a fixed port number (for example, 32493):

MCP_CLIENT_SECRET=<YOUR_CLIENT_SECRET> claude mcp add --transport http --callback-port <PORT> mulesoft-platform https://omni.mulesoft.com/mcp --client-id <YOUR_CLIENT_ID>

Using a fixed callback port ensures the redirect URL remains consistent across sessions. Without a fixed port, Claude Code assigns a random port for each authentication request, which causes authorization to fail because the connected app requires an exact URL match.

In your connected app:

  1. Log in to Anypoint Platform, and open your connected app.

  2. In the Redirect URLs field, enter http://localhost:<PORT>/oauth/callback, using the same port number you specified in the command (for example, http://localhost:32493/oauth/callback).

  3. To apply changes, click Continue.

Install Claude Code.

ChatGPT

In ChatGPT:

  1. Click Apps > Settings.

  2. Click the settings icon, click Create App, and configure the following:

    1. Name the connection, and enter the Remote Universal URL, for example, https://omni.mulesoft.com/mcp.

  3. In OAuth > Advanced settings > Client registration, configure the following:

    1. Enter the Client ID and Client Secret from your connected app.

    2. Copy the Callback URL.

In your connected app:

  1. Log in to Anypoint Platform, and open your connected app.

  2. In the redirect URLs field, enter the Callback URL value you copied.

  3. To apply changes, click Continue.

Download ChatGPT.

Cursor

In Cursor:

  1. Click Settings > Tools and MCPs > Add a Custom MCP Server.

  2. Add the following code snippet, replacing <PORT> with a fixed port number (for example, 32493):

    {
      "mcpServers": {
        "mulesoft-platform": {
          "command": "npx",
          "args": [
            "-y",
            "mcp-remote@latest",
            "https://omni.mulesoft.com/mcp",
            "<PORT>",
            "--static-oauth-client-info",
            "{\"client_id\":\"YOUR_CLIENT_ID\",\"client_secret\":\"YOUR_CLIENT_SECRET\"}"
          ]
        }
      }
    }

Using a fixed port ensures the redirect URL remains consistent across sessions. Without a fixed port, Cursor assigns a random port for each authentication request, which causes authorization to fail because the connected app requires an exact URL match.

In your connected app:

  1. Log in to Anypoint Platform, and open your connected app.

  2. In the Redirect URLs field, enter http://localhost:<PORT>/oauth/callback, using the same port number you specified in the configuration (for example, http://localhost:32493/oauth/callback).

  3. To apply changes, click Continue.

Download Cursor.

Windsurf

In Windsurf:

  1. Click Settings > Cascade > Open MCP Registry.

  2. Click the settings icon and in ~/.codeium/windsurf/mcp_config.json add the following code snippet, replacing <PORT> with a fixed port number (for example, 32493):

    {
      "mcpServers": {
        "mulesoft-platform": {
          "command": "npx",
          "args": [
            "-y",
            "mcp-remote@latest",
            "https://omni.mulesoft.com/mcp",
            "<PORT>",
            "--static-oauth-client-info",
            "{\"client_id\":\"YOUR_CLIENT_ID\",\"client_secret\":\"YOUR_CLIENT_SECRET\"}"
          ]
        }
      }
    }

Using a fixed port ensures the redirect URL remains consistent across sessions. Without a fixed port, Windsurf assigns a random port for each authentication request, which causes authorization to fail because the connected app requires an exact URL match.

In your connected app:

  1. Log in to Anypoint Platform, and open your connected app.

  2. In the Redirect URLs field, enter http://localhost:<PORT>/oauth/callback, using the same port number you specified in the configuration (for example, http://localhost:32493/oauth/callback).

  3. To apply changes, click Continue.

Download Windsurf.

VS Code

In VS Code:

  1. In your user profile, configure a custom MCP server in the mcp.json file. Alternatively, run MCP: Add Server in the Command Palette (Shift+Cmd+P) to add a server through a guided flow. Replace <PORT> with a fixed port number (for example, 32493):

    {
      "servers": {
        "mulesoft-platform": {
          "type": "stdio",
          "command": "npx",
          "args": [
            "-y",
            "mcp-remote@latest",
            "https://omni.mulesoft.com/mcp",
            "<PORT>",
            "--static-oauth-client-info",
            "{\"client_id\":\"YOUR_CLIENT_ID\",\"client_secret\":\"YOUR_CLIENT_SECRET\"}"
          ]
        }
      }
    }

Using a fixed port ensures the redirect URL remains consistent across sessions. Without a fixed port, VS Code assigns a random port for each authentication request, which causes authorization to fail because the connected app requires an exact URL match.

In your connected app:

  1. Log in to Anypoint Platform, and open your connected app.

  2. In the Redirect URLs field, enter http://localhost:<PORT>/oauth/callback, using the same port number you specified in the configuration (for example, http://localhost:32493/oauth/callback).

  3. To apply changes, click Continue.

  4. To run the server, click Start.

  5. When prompted, enter the Client ID and Client Secret from your connected app.

Download VS Code.

Troubleshooting

Resolve authentication and connection issues with these troubleshooting steps.

Authentication Failure

To resolve authentication issues, follow these troubleshooting steps.

  • Try logging out of your Anypoint Platform account and logging back in.

  • If you encounter an authorization error:

    • Add the correct redirect URL to your connected app.

    • Add the necessary permissions scopes to your connected app.

  • If authorization fails due to a redirect URL mismatch:

    • IDE-based clients (Claude Code, Cursor, Windsurf, VS Code) use a localhost callback URL with a port number. If the port changes between sessions, the redirect URL no longer matches the one registered in your connected app. To prevent this, configure a fixed callback port as described in Configure Your IDE. Then add the matching localhost URL to your connected app’s redirect URLs (for example, http://localhost:32493/oauth/callback).

  • If you get a permissions-related error when attempting to authenticate, add these permissions to your connected app:

    • Background Access

    • Profile

    • Identity

    • Email

Connection Issues

If your MCP client can’t reach the server or fails to establish a session, verify these settings.

  • Ensure your MCP client supports Streamable HTTP transport.

  • Check that your client can handle OAuth authentication flows.

  • Verify the MCP server URL is https://omni.mulesoft.com/mcp.