Patch Changes
- #409
de1f0a6Thanks @mattzcarey! - Accept a resource indicator that names the protected resource's URL with extra query parameters. An MCP client configured withhttps://mcp.example.com/mcp?mode=directsends that URL asresource; the protected route already covers it (it accepts the resource's tokens and points its 401 at the resource's metadata), but/authorizeand/tokenrejected it withinvalid_target. The value now maps to the configured resource, which stays the token audience. Path, port and the resource's own query parameters remain strict.