Audit draft spec changes

[findleyr]

Reminder issue: prior to the v1 release, we should really audit upcoming spec changes to ensure that at least the next spec will not cause us to introduce awkward APIs, or breaking changes...

I'll do an audit this week.

[findleyr]

Thus far, there are two major changes in the draft schema:

• SEP-973: Expose additional metadata for Implementations, Resources, Tools and Prompts modelcontextprotocol#955 is not a problem, since we have consistently used mcp.Implementation in our server/client construction.
• @jba could you take a look at feat: enhance auth server discovery with OAuth2 and OpenID metadata support modelcontextprotocol#797? Does its shape impose any constraints on our current API?

[jba]

modelcontextprotocol/modelcontextprotocol#797 does not affect our API.

It would require some minor behavior changes to https://github.com/modelcontextprotocol/go-sdk/blob/main/internal/oauthex/auth_meta.go#L126, but we haven't even exposed that yet.

What we do expose, or will, doesn't implement that part of the flow anyway.

[jba]

I added #472 and #473 to make sure we implement the changes in the draft.

[jba]

since we have consistently used mcp.Implementation in our server/client construction

A great example of future-proofing against the spec.

If you're confident you've found all the draft changes, can we close this? Or would you like me to make a pass over the draft spec?

[findleyr]

If you're confident you've found all the draft changes, can we close this? Or would you like me to make a pass over the draft spec?

Hah, I thought I'd already done that, but hadn't clicked the button.
It's still possible that there are last-minute spec changes (I'm concerned about modelcontextprotocol/modelcontextprotocol#1442 and modelcontextprotocol/modelcontextprotocol#1364). However, there's nothing we can do about those until they're accepted (other than opining on them).