Apache SkyWalking's MCP server moves to the official Go SDK and adds 2026-07-28 support on master

The Apache SkyWalking project merged a rewrite of its MCP server's protocol layer on 2026-08-14. Pull request #44 replaced the server's existing MCP plumbing with the official modelcontextprotocol/go-sdk, a change of 1,958 added and 2,233 deleted lines across 56 files, and go.mod on master now requires that SDK at v1.7.0.

The project's changelog states what the migration bought. Under a 0.3.0 heading, it says the server gained support for the 2026-07-28 revision and that "clients on earlier revisions keep working: the server answers both the per-request _meta model and the legacy initialize handshake on the same endpoint". That dual-era serving is the same migration pattern the C# SDK shipped as HttpServerSessionMode on 2026-08-13 and the Ruby SDK described as an era lock on 2026-08-15, arriving here in a server rather than an SDK.

Two other changes are listed alongside it. Tool input schemas are now inferred from the Go request structs rather than declared separately, so a schema cannot drift from the type it describes, and required tool parameters are enforced instead of silently falling back to a default time window. The MQE documentation resources were removed on the grounds that clients rarely read them.

None of this has shipped in a release. The repository's tags run v0.1.0-rc0, v0.1.0 and v0.2.0, with nothing for 0.3.0, so the changelog section describes work on the default branch. MCP News records the server's spec support as unverified until a release carries it.