Improve MCP-Go stability #555
Description
Hi ✋
Thank you for all the work you’ve put into the library. It has been a great starting point for many of us implementing MCP servers in Go, and we really appreciate the foundation it provides.
As early adopters of MCP-Go, we ran into a few challenges around quality and reviews that we initially assumed were part of the bootstrapping phase. In particular, we’ve occasionally encountered leaks and regressions, such as:
- bug: Incorrect sampling handling leads to errors and superfluous response write call #554
- Deadlock when adding Tools concurrently #138
- Panic on shutdown of session and server #173
However, in our opinion the project has now moved beyond the early bootstrapping stage and the project is considered for production use cases, and these kinds of issues are becoming more impactful. That’s why we think the next step could be to strengthen the review process. This could mean having dedicated code owners with strong Go expertise and introducing code coverage tools to ensure the most critical paths are thoroughly tested, so that issues can be caught earlier.
Another potential approach could be adopting a beta or next-version release strategy, where new changes can be tested in a safer environment before being promoted as stable. This could help balance fast iteration with more reliable releases.
Thanks again for making MCP-Go available. We are excited to see how it continues to evolve. We will continue contributing to the project and are also willing to sponsor.