Cursor MCP timeout activation stops SonarQube MCP Server

SonarQube Server / Community Build
,
1

Hi everyone,

First of all, thank you for building this project.

  • MCP Server: Docker
  • IDE: Cursor 2 (2.0.77)
  • SonarQube Server: 2025.10 community edition.

I’m trying to start MCP Server on Cursor connecting to my SonarQube Server on AWS EC2 behind ALB.

I tried to start the MCP server following the Cursor configuration guide, but after about a minute the process stopped and the MCP failed to activate. So, as a test, I activated a local version of SonarQube Server, and the MCP server started instantly. Very strange.

Then I reviewed the MCP server code and noticed that during the initialization process, the service downloads plugins sequentially from SonarQube Server. In my case, the download is at least 260MB, and I imagine that due to my connection speed, it takes at least 6 minutes.

At first, I thought it was my ALB timeout, but when I ran the code in Java, I saw that the download works correctly. Even if I run the container from the terminal, the download proceeds. After doing some research, I discovered that the MCP protocol has an issue with its initialization time:

Anyway, it would be great if the plugin downloads were asynchronous and didn’t interrupt the MCP initialization process.I would greatly appreciate it if this update could be implemented.

Thank you in advance for your consideration.

4

Hey @jose.af , you’re absolutely right about your assumptions, thanks for bringing this up.

We’re going to work on introducing an asynchronous startup and dynamically registering tools as they become available. This should help avoid the timeout issues.

In the latest release, I’ve already made an improvement to download only the analyzers we actually use, which has significantly reduced startup time. That said, I agree this still isn’t the ideal workflow. As mentioned above, you can expect further improvements in the next release.

Thanks for your patience!

3 Likes
5

Nice, thanks for the update and for addressing this!

1 Like
6

Hey @jose.af, sorry for the slight delay, our Docker image just got updated. Could you please give it a try and see if you still experience any issues?

1 Like
7

Hello @nicolas.quinquenel. Compared to any other project, you really didn’t take any time at all. I just tested it and everything goes very good. Thank you so much for making it happen.

1 Like