Why do you still use mcp-go when an official Go SDK exists?

[ezynda3]

When I first built this library, I built it for myself and never expected it to become as popular as it has. A lot of big names started using mcp-go for their servers. Github notably was one of the first big adopters. They and other projects have slowly started moving over to the official SDK. I don't blame them as Google obviously has the dev resources to maintain the lib and keep up with new versions of the spec. There are still quite a few people that use mcp-go though and still contribute through PRs and issues. I would just like to understand the value proposition this package has over the official package. I have no plans to archive this package at the moment. I still use it for my own projects but just want to get a better idea from people that aren't as biased as I am.

Cheers!
Ed