CAST IMAGING – V3 – MCP Server – VS CODE - Error Connecting .. for async notifications will retry

When attempting to use MCP server in VS Code getting “Error Connecting .. for async notifications will retry”

Action Plan

1. Check if the async stream connection is not getting terminated by an intermediate network component ,which could be a proxy, firewall, or even timeout, which results in automatic reconnection attempts.
2. Check if only one MCP server instance is running. Ensure VS Code didn’t start multiple copies during reloads.
3. Check whether there are any port/socket conflicts. Confirm that only one server process is bound and handling both sync and async connections.

4. Check if the MCP server has not crashed after async connect. Check the logs for any errors.

    

NB: The default log path is: \ProgramFiles\CAST\Imaging-MCP-Server\logs

Default installation path is: \ProgramData\CAST\Imaging-MCP-Server\setup-config

Resources

Getting started with CAST Imaging MCP Server

CAST Imaging v3 Product Documentation

CAST Imaging Troubleshooting Guides

Additional Resources

CAST Highlight Product Documentation

CAST Highlight Troubleshooting Guides

Ticket

56293