Migrate to official Go MCP SDK

[umairidris]

Describe the feature or problem you’d like to solve

Currently the GitHub MCP server uses a community maintained MCP implementation: https://github.com/mark3labs/mcp-go

The official MCP SDK for Go is now available and had its first stable launch: https://github.com/modelcontextprotocol/go-sdk.

Proposed solution

Migrate to the official Go MCP SDK for better consistency and interoperability.

[findleyr]

👋 I'm one of the maintainers of the official SDK. Please be vocal as you do this migration. You may be the largest Go MCP server, and we'll prioritize any issues or missing features you encounter during your migration.

[omgitsads]

@findleyr thanks for reaching out. I had previously investigated this back in July and found there wasn't a ton preventing us from the OSS side of things to move to the Go SDK. I need to look again at Resources, as that didn't immediately translate as easily as Tool support did.

The main thing preventing us from moving forward at that point was modelcontextprotocol/go-sdk#148, which is still the case. I need to look into implementing the Mcp-Session-Id wrapper with GetSessionId().

[findleyr]

Thanks. As you analyze, can you please let me know what specifically you need from distributed sessions?
We support stateless sessions, but don't (yet) provide APIs that would allow storing/retrieving client capabilities.