fix: Connect error in URL elicitation example

[nbarbettini]

Motivation and Context

Fixes an error noticed by @cliffhall in this PR: #1105 (comment)

How Has This Been Tested?

Working as expected once again:

Breaking Changes

n/a

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Checklist

• I have read the MCP Documentation
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have added or updated documentation as needed

Additional context

Problem: To create src/examples/client/elicitationUrlExample.ts I copied some code from src/examples/client/simpleOAuthClient.ts, but I copied older code that was later cleaned up and refactored.

Solution: Adopting the better connect() pattern from simpleOAuthClient.ts made the problem go away.

The real root cause was:

            requestInit: {
                headers: {
                    'Content-Type': 'application/json',
                    Accept: 'application/json, text/event-stream'
                }
            }

which clashed with 'Content-Type': 'application/x-www-form-urlencoded' set in exchangeAuthorization() in src/client/auth.ts. I believe it might be useful to normalize header case-sensitivity in createFetchWithInit(), but that is deeper than I want to go in this PR! 🙂

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/modelcontextprotocol/typescript-sdk/@modelcontextprotocol/sdk@1136

commit: 044f109

[KKonstantinov]

Thanks for the quick follow up

[felixweinberger]

Hi @nbarbettini thanks for the quick fix!

Was just going to merge this, but looks like maintainerCanModify is false on this branch so I can't update branch to merge in main - mind doing that today so we can get this into the release?

[nbarbettini]

Fixed! Thanks @felixweinberger