MCP sign-in no longer saves a stale client secret or redirect address back to disk.
What's wrong with this entry?
Saving OAuth client details for an MCP server now drops the client secret when the issuer is known, the client id matches the one already stored with no secret against it, and it matches the configured oauth.clientId. A previously stored redirect URI is only reused when this client is not doing the redirect itself, instead of falling back to the current one.
- Prevents a secret from a different registration being written back over a secretless entry.
mcpOAuth
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.228
Bundled API client: new endpoints and a stripped request field
Both mention client
-
v2.1.228
Bundled Anthropic SDK picks up beta resources
Both mention client
-
v2.1.228
API client request handling moved to a middleware chain
Both mention client