---
schema_version: "1"
id: 273225b4621ff52923c74bffadf1436b786da27ba6a63755c5c08f31b33ee8c7
title: MCP Server Issues
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/anypoint-code-builder/troubleshoot-mcp-server.md
canonical_url: https://docs.mulesoft.com/anypoint-code-builder/troubleshoot-mcp-server
source_site: docs.mulesoft.com
content_type: documentation
content_hash: fb50ed0b78b03ab71837668fbb84bb6a86422310c433ddf6dff2ce6e3a7eb3ea
description: MuleSoft Documentation Site
latest: true
---
---
product: Anypoint Code Builder
version: master
---

# MCP Server Issues

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

When using the MuleSoft MCP Server in Anypoint Code Builder, you might encounter issues that prevent
the server from functioning correctly. Follow these troubleshooting steps to diagnose and resolve
common MCP server problems.

## Verify the MCP Server Is Running

If MuleSoft Vibes isn’t responding to commands or tools aren’t available, verify that the MuleSoft
MCP Server is running:

1.  Open the MuleSoft Vibes panel in Anypoint Code Builder.

2.  Click **Manage MCP Servers**.

3.  Click ![](/mulesoft/current/en-us/anypoint-code-builder/_images/icon-gear.png) (Settings) to open the MCP Server settings.

4.  In the **Installed** tab, verify that the MuleSoft MCP Server is enabled (toggled on and marked
    in green).

    If the server is disabled, toggle it on to enable it.

    ![The MCP server panel showing the Settings icon and the Enable toggle.](/mulesoft/current/en-us/anypoint-code-builder/_images/mcp-server-settings.png)

## Verify MuleSoft MCP Server Tools in GitHub Copilot

When you install Anypoint Code Builder, the MuleSoft MCP Server tools are automatically registered
in VS Code. To confirm the tools are available in GitHub Copilot:

1.  Make sure GitHub Copilot is set up and you are logged in. For setup instructions, see
    [Use MuleSoft MCP Server Tools with GitHub Copilot](https://docs.mulesoft.com/anypoint-code-builder/vibes-mcp-server#use-mcp-tools-copilot).

2.  Follow the VS Code instructions to
    [use MCP tools in agent mode](https://code.visualstudio.com/docs/copilot/customization/mcp-servers#_use-mcp-tools-in-agent-mode)
    and confirm that the MuleSoft tools appear in the tools list.

    > [!NOTE] The tools are registered directly in VS Code using the Language Model API. No manual
    > configuration is required.

## Check MCP Server Logs

When the MCP server isn’t working as expected, check the logs to identify the cause:

1.  Open the Output panel.

    Show me how

    - Use the keyboard shortcuts:

      - Mac: Cmd+Shift+u

      - Windows: Ctrl+Shift+u

    - Select **View** > **Output**.

2.  From the dropdown list in the Output panel, select **Anypoint Code Builder - MCP Server**.

    ![The outputs panel showing the MCP Server selected in the dropdown menu.](/mulesoft/current/en-us/anypoint-code-builder/_images/mcp-server-output-dropdown.png)

3.  Review the logged information for errors or warnings.

    The logs provide details about server operations, tool executions, and any errors that occur.

You can also check the **Tasks** section in the Output panel for additional errors or warnings
related to MCP server operations.

## Restart the MCP Server

If the MCP server stops responding or behaves unexpectedly, restart it:

1.  Open the MuleSoft Vibes panel in Anypoint Code Builder.

2.  Click **Manage MCP Servers**.

3.  Click ![](/mulesoft/current/en-us/anypoint-code-builder/_images/icon-gear.png) (Settings) to open the MCP Server settings.

4.  In the **Installed** tab, locate the MuleSoft MCP Server.

5.  Click ![](/mulesoft/current/en-us/anypoint-code-builder/_images/icon-restart-mcp-server.png) (Restart Server).

    When the server restarts successfully, you see a confirmation message in the Output panel.

If restarting doesn’t resolve the issue, try disabling and then re-enabling the server.

## Validate MCP Server Configuration

You can validate whether the MCP server is running correctly by using third-party tools:

1.  In the MCP Server settings, select **Configure MCP Servers** to view the server configuration.

2.  Use an API client like Postman to send test requests to the MCP server endpoint.

3.  Verify that the server responds correctly to your requests.

If the server doesn’t respond, check that the configuration in the `a4d_mcp_settings.json` file is
correct.

## MCP Server Tools Are Unavailable

If MCP server tools aren’t appearing or aren’t responding:

1.  Verify that the MuleSoft MCP Server is enabled in the **Installed** tab of the MCP Server
    settings.

2.  Check that the tools are enabled for the server:

    1.  In the **Installed** tab, select the MuleSoft MCP Server to expand its details.

    2.  Verify that the required tools are listed and enabled.

3.  Restart the MCP server.

4.  If the issue persists, check the MCP server logs for errors.

## MCP Server Request Timeout

If requests to the MCP server are timing out:

1.  Open the MCP Server settings.

2.  In the **Installed** tab, select the MuleSoft MCP Server.

3.  Locate the **Request Timeout** setting.

4.  Increase the timeout value to allow more time for the server to respond.

For complex operations, a longer timeout might be required.

## See Also

- [Configuring an MCP Server](https://docs.mulesoft.com/anypoint-code-builder/vibes-mcp-server)

- [Troubleshooting](https://docs.mulesoft.com/anypoint-code-builder/troubleshooting)

- [Troubleshooting AI Features in Anypoint Code Builder](https://docs.mulesoft.com/anypoint-code-builder/troubleshoot-generative-ai)

- [Known Issues](https://help.salesforce.com/s/issues)