modelcontextprotocol / modelcontextprotocol/typescript-sdk
SDK assumes one authorization server to be used from PRM
Open
Nobody has claimed this yet.
auth
bug
enhancement
P3
ready for work
- Dominant language
- TypeScript
- Stars
- 13.4k
- Forks
- 2.2k
- Avg merge
- 3d 15h
- Merged PRs (30d)
- 4
Description
Describe the bug
This is the current logic:
if (resourceMetadata.authorization_servers && resourceMetadata.authorization_servers.length > 0) {
authorizationServerUrl = resourceMetadata.authorization_servers[0];
}
SDK should offer a way for developers to specify which of the authorization servers to use from the PRM document.
Expected behavior
SDK offers an affordance through which the authorization server can be chosen.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the PRM handling that contains the shown authorization_servers[0] selection and trace how authorizationServerUrl is consumed. Determine the SDK affordance needed to let developers choose an authorization server, then verify that the resulting behavior uses the selected server rather than always choosing the first entry.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- authentication
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100