[NFR] Migrate to Go-SDK

[manusa]

Description

The first stable release of Model Context Protocol Go SDK is projected for August 2025.

To be able to keep up with the latest spec changes, we should migrate the server side to the new SDK as soon as it's GAd.

References

• Original Proposal: https://github.com/orgs/modelcontextprotocol/discussions/364
• Go-SDK 2025-06-18 spec compliance:
  2025-06-18 spec support modelcontextprotocol/go-sdk#2
• Tool Binding APIs
  Tool binding APIs modelcontextprotocol/go-sdk#37

[Cali0707]

Hey @manusa - the Go SDK is expected to GA in the next few days. I'm happy to work on a PR here to do the migration in kubernetes-mcp-server

[manusa]

Hey @Cali0707

Thank you very much.
We already have a few branches with some initial migration.
The idea is to do migration by parts. You might have already noticed how toolsets and tool definitions are completely decoupled from the underlying MCP server.

The next step is switching the production code in pkg/mcp to use Go-SDK with the minor amount of changes.
Once that's done, leveraging some of the Go-SDK specific features would be the next step.

I'm sure you can help out with some of these tasks.
Besides waiting for the GA, we also need to cut a stable release with the toolsets feature, so the work on the migration might still be delayed a few more days.