modelcontextprotocol / modelcontextprotocol/typescript-sdk
Implement SEP-1649: MCP Server Cards (.well-known Discovery)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.4k
- Forks
- 2.2k
- Avg merge
- 3d 15h
- Merged PRs (30d)
- 4
Description
This is a tracking issue for implementation of SEP-1649.
Summary
This SEP introduces a standardized mechanism for MCP servers to advertise their capabilities and identity through .well-known URLs following established internet standards for service discovery. The TypeScript SDK needs to implement support for publishing capability documents at standardized .well-known paths describing available tools, resources, and prompts, enable clients to fetch these documents via HTTP without establishing a full MCP session, and provide utilities for both server-side capability document generation and client-side capability document fetching and parsing to enable better server discovery and selection UX.
Related Issues & PRs
- Implementation PRs: n/a
- Related PRs: n/a
- Related Issues: n/a
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 reading SEP-1649 and the TypeScript SDK context described in this issue. Define the server-side document generation and client-side HTTP fetching and parsing scope, including standardized .well-known paths and advertised tools, resources, and prompts. Done means the SDK supports publishing and retrieving capability documents without a full MCP session.
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
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100