modelcontextprotocol / modelcontextprotocol/ext-server-card
Incorporate comprehensive auth scenarios into Server Card spec
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 8
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
@tobinsouth raised a number of auth-related shape concerns here: https://github.com/modelcontextprotocol/modelcontextprotocol/pull/2742
We should incorporate those into the Server Card shape, to the extent where we agree they make sense.
I think we should:
- Immediately do a quick pass to make sure nothing in the current draft is backwards incompatible with the concerns he's raised
- Finalize the initial SEP with a limited shape, formalizing this extension
- Then as a fast follow work to expand our shapes to fully support all of Tobin's scenarios
I'd rather do 2 before 3, so we don't introduce a whole lot of new fields into server.json as part of this Server Card formalization out of the gate. Better to propose and collect some community feedback before we lock them in.
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
Review the concerns in pull request #2742 alongside the current Server Card draft and the existing server.json shape. Check whether the draft is backwards compatible, then use the issue's proposed order to define a limited initial SEP before considering broader scenarios. Done means the agreed initial shape is formalized without prematurely adding the wider set of fields.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100